GARCIA Clément

@AlbertoMonteiro you can contribute :)

You can create your own validation rules to check this.

I have exactly the same problem than @nonahex with a Moto X 2nd gen (XT1092).

Hi 👋 +1 about the comment just above, I also encounter this crash on Android 11 devices. I'm catching the exception but if the library could handle it in a...

Thanks for your answers and your work on this library 🙏 I'll see with the latest release if this is something still being reported in production environment or not 🙂

Thanks to the last merge of the #131 patch, I am now able to send an receive messages with Teensy. But please note that I had to configure the IRQ...

The communication between Arduino Pro Minis is also working even if I add this pinMode configuration, so yes, I will make a pull request to add this and fix the...

Unfortunately I still get a lot of clock errors and they are not due to a bad contact or wires (the same breadboard and cables are working perfectly with Pro...

Hey 👋 Same crash reports here: ``` Fatal Exception: java.lang.NullPointerException: at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:116) at java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:640) at com.onesignal.OSTaskController.startPendingTasks(OSTaskController.java:92) at com.onesignal.OneSignal.init(OneSignal.java:885) at com.onesignal.OneSignal.setAppId(OneSignal.java:737) at com.onesignal.OneSignal.reassignDelayedInitParams(OneSignal.java:1181) at com.onesignal.OneSignal.onRemoteParamSet(OneSignal.java:889) at com.onesignal.OneSignal$7.complete(OneSignal.java:1122) at com.onesignal.OneSignalRemoteParams.processJson(OneSignalRemoteParams.java:211) at com.onesignal.OneSignalRemoteParams.access$100(OneSignalRemoteParams.java:12)...

@emawby No I didn't reproduce it on my side, that's the kind of error reported in Crashlytics but quite hard to spot on a few dev devices. And since I...