Closed zarko-tg closed 2 years ago
@zarko-tg,
Hi, checking it.
The same here.
@zarko-tg @vvarda
Fixed with the latest release.
@zarko-tg thanks.
:beer:
hi ! I'm getting the same error. Can you please tell how you fixed it ? E/ResolverController: No valid NAT64 prefix ?
@officialyashx
What we fixed was the exception below:
05-24 10:58:00.532 12138 12138 E AndroidRuntime: FATAL EXCEPTION: main 05-24 10:58:00.532 12138 12138 E AndroidRuntime: Process: com.company.app.test, PID: 12138 05-24 10:58:00.532 12138 12138 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/pushwoosh/PushwooshPlatform;
No valid NAT64 prefix was just a warning back then.
hi ! I'm getting the same error. Can you please tell how you fixed it ? E/ResolverController: No valid NAT64 prefix ?
Can you help me if u have resolve this error
hi ! I'm getting the same error. Can you please tell how you fixed it ? E/ResolverController: No valid NAT64 prefix ?
Can you help me if u have resolve this error Any luck with this error? I am having the same issue as well
hi ! I'm getting the same error. Can you please tell how you fixed it ? E/ResolverController: No valid NAT64 prefix ?
Can you help me if u have resolve this error Any luck with this error? I am having the same issue as well
No luck with this error
@allensoberano @15NiKhIl I've just tried reproducing the crash, and it worked fine on my end.
Could you please share complete console logs from the moment when you launch your app and until the crash occurs? Also, by any chance is it possible for you to share a simple reproducer project so we could investigate the issue on our side?
It would also help if you could specify what Android versions and what device models are affected, as well as your cordova-android version.
2022-04-06 12:30:02.222 1892-1892/? E/netmgr: Failed to open QEMU pipe 'qemud:network': Invalid argument 2022-04-06 12:30:02.380 1907-1907/? E/wifi_forwarder: RemoteConnection failed to initialize: RemoteConnection failed to open pipe 2022-04-06 12:30:06.393 2676-6556/com.google.android.gms.persistent E/WakeLock: GCM_HB_ALARM release without a matched acquire! 2022-04-06 12:30:48.717 2015-2054/system_process E/memtrack: Couldn't load memtrack module 2022-04-06 12:30:48.717 2015-2054/system_process W/android.os.Debug: failed to get memory consumption info: -1 2022-04-06 12:30:52.679 2015-2386/system_process D/WificondControl: Scan result ready event 2022-04-06 12:31:00.005 2166-2166/com.android.systemui D/KeyguardClockSwitch: Updating clock: 1231 2022-04-06 12:31:02.223 1892-1892/? E/netmgr: Failed to open QEMU pipe 'qemud:network': Invalid argument 2022-04-06 12:31:02.441 1907-1907/? E/wifi_forwarder: RemoteConnection failed to initialize: RemoteConnection failed to open pipe 2022-04-06 12:31:06.395 2676-2676/com.google.android.gms.persistent W/GCM: Heartbeat timeout, GCM connection reset -2 2022-04-06 12:31:06.402 2676-7826/com.google.android.gms.persistent E/WakeLock: GCM_HB_ALARM release without a matched acquire! 2022-04-06 12:31:06.402 2676-7826/com.google.android.gms.persistent W/WakeLock: GCM_HB_ALARM counter does not exist 2022-04-06 12:24:31.319 2506-3581/com.google.android.apps.nexuslauncher E/ActivityThread: Failed to find provider info for com.goo
Can someone help how to resolve?
This will likely affect all your Android users, not just apps using the Cordova plugin, but I am posting the issue here since we use this plugin in an Ionic Angular app.
Google (Play) are demanding 64-bit compliance starting August 1, 2019: https://developer.android.com/distribute/best-practices/develop/64-bit
We just tried running a pure ARM 64-bit build (arm64 / arm64-v8a) of our app on a Google Pixel phone which results in a crash every time the app is installed anew and launched. Further launches do not manifest the crash.
It seems it might be a problem with the Inbox component/dependency even though we don't use it as a feature.
Some info: pushwoosh-cordova-plugin 7.14.0 cordova CLI 9.0.0 cordova-android 8.0.0
(We'll probably be also releasing a x86_64 version but that has been tested yet (at least on emulator))
Here is pretty much the full device log before and after the crash: