Thunkable Classic (app.thunkable.com) and Android 8 / API 26 / SDK 26

[Goldking]

I have the same problem with onesignal. It works right up to android 7, android 8 get error and app crashes when is in background. The message works right if app is running. Onesignal tell me to speak with thunkable team
@amrita
Thanks .

[Comitato_Genitori_Ma]

this silence is worrying, I have only mistaken argument or there are no answers about it?

[Comitato_Genitori_Ma]

I’m sorry if I mentioned several people in my post, I just asked the help of the “experts” who had commented before

[arun]

This is something that we are working on at the moment. Hopefully we will have some updates to share in the next few days.

[Comitato_Genitori_Ma]

Thanks @Arun, I look forward to updates

[Goldking]

We are waiting for and thanks for all your work

[ColinTree]

I have problems on this component only on Android 8.0 devices

I have the same problem with onesignal

Hi there, I’m looking into this and find hard to reproduce. If you can provide some sample crash log from your users and it will be really helpful! Thanks

[Goldking]

Thanks I will try but I think it’s hard. App and one signal works fine when I test live with thankable (because app is open) , the problem is when I download the app and send a message (when app is closed) , my device with android 8 show the default message of app crashed. If app is opened massage appears correctly on the screen. Down to android 8 works good

With app opened works fine

With app closed or in background this is the only message we can detect

[nono_neno]

Hi
I have this problem

Your app currently targets API level 25 and must target at least API level 26 to ensure it is built on the latest APIs optimized for security and performance. Change your app’s target API level to at least 26

[Ratthanin]

got the problem here too, notification window is looking ugly also.

[solo]

I’ve been suffering from the same issue since August. I lost a lof of users because of that and stopped using the onesignal component. Here are screenshots of Stack traces

[Comitato_Genitori_Ma]

Sorry @solo now that you no longer use onesignal have you stopped using notifications or have you found alternative ways? I have the same problem and above all I should develop something that is compile also for iOS

[solo]

Unfortunately, I don’t use notifications anymore which is really bad because it was an important feature in my apps. I wish they would fix the problem of Onesignal very soon!

[wei]

I believe I have a reasonable fix. Can you share your OneSignal App ID with me? I can build the apk and send it back to you for testing.

Please email it to me at wei@thunkable.com

Best,
Wei

[solo]

Thank you! I sent you my app ID by email.

[wei]

I believe I fixed the bug/crash in Android OS 8 and above. If you have a phone with Android OS 8, can you install the apk below and put it on the background? I want to send you a push notification

Here is the apk link -
https://drive.google.com/open?id=1pofAPyyDfVBqVwvzLSqdljKw8Ez_fNiX

Thanks,
Wei

[domhnallohanlon]

Works well for me anyway. Can anyone else verify?

@solo
@Ratthanin
@nono_neno

[Comitato_Genitori_Ma]

Sorry @wei, it means that the bug on the component has been fixed or only on the @domhnallohanlon app?

[Ratthanin]

My phone is Huawei P20 Android 8

• never got any notification alert from onesignal if app was closed.

• got notification only while the app was running and looking ugly. (screenshot1)
  

  

• notification number on the icon was frozen and never changed no matter how many notifications was sent from Onesignal (screenshot2)
  
  and not equal to real notification message ( screenshot3 )
  

  

• I have the same apple app build with swift run on Iphone and get notification message from OneSignal at the same time, it works fine.(screenshot4)
  

  

[domhnallohanlon]

Hi @Ratthanin, you need to install @wei’s test app so we can confirm that the new update is working.

Thanks