Eugene Maning
Eugene Maning
What worked for me was the following: * Remove Podfile.lock * then `pod install`
Ughhh so this is M1 issues. Think we can resolve this soon?
Hi @jdoroy-808 yes. It should be setup properly for Android.
The proposed solution also didn't work for me. Anyone else figured it out?
In my case adding `defaultOption` makes it unable to change value onSelect.
@hoaphantn7604 I hope you can help on this matter fast. Quite troublesome. I tried many different implementations of the stack, all the same.
Hope this helps... ``` Exception in native call java.lang.Exception: Must call 'initWithContext' before use at com.onesignal.internal.OneSignalImp.getInAppMessages(OneSignalImp.kt:107) at com.onesignal.OneSignal.getInAppMessages(OneSignal.kt:78) at com.onesignal.rnonesignalandroid.RNOneSignal.removeHandlers(RNOneSignal.java:166) at com.onesignal.rnonesignalandroid.RNOneSignal.onCatalystInstanceDestroy(RNOneSignal.java:210) at com.facebook.react.bridge.BaseJavaModule.invalidate(BaseJavaModule.java:76) at com.facebook.react.bridge.ModuleHolder.destroy(ModuleHolder.java:110) at com.facebook.react.bridge.NativeModuleRegistry.notifyJSInstanceDestroy(NativeModuleRegistry.java:108) at com.facebook.react.bridge.CatalystInstanceImpl$1.run(CatalystInstanceImpl.java:359)...
Wow this is a weird one
> I don't stand with casting. Casting, for me, just means you lie to the compiler. > > `@ts-expect-error` works differently from `@ts-ignore`, if the problem has been fixed, `@ts-expect-error`...