Cordova application - notification not working for 64 bit signed apk

Follow

Hi,

Are devices on the 64-bit application generating Channel ID?

Send us your App Key, a Push ID of a test send and a Channel ID of any device you are testing on using this form and we'll take a closer look.

Thanks,

Jay M.
Airship Technical Support

Hi,

After testing extensively, we found that notification is not working for only 2 test devices, which were continuously used for testing our app.

When tried to test notifications through "Test Push" it worked as expected. 

But it is still not working when pushed from app server. 

Is there a way to figure out what is the issue ? 

See the information I requested in the last comment.

Jay M.
Airship Technical Support

Thanks for your help.  Please can you close this support help request.  Thank you.

I understand that you recently upgraded a Cordova application that utilizes Urban Airship (UA) for notifications to make it compatible with 64-bit Android devices. However, you're facing an issue where notifications are not being received on the upgraded 64-bit application once it is signed. It's interesting to note that notifications are successfully received on the 32-bit signed and unsigned APKs, as well as the 64-bit unsigned APK.

I upgraded our Cordova mobile application to support 64-bit Android devices and integrated Urban Airship (UA) for notifications. We've encountered an unexpected issue where notifications are not being received on the upgraded 64-bit version after it's been signed. Interestingly, notifications are successfully delivered on both the 32-bit version (both signed and unsigned) and the 64-bit version when it's unsigned. This suggests that the notification infrastructure is functioning, but there might be a specific configuration or setting affecting the 64-bit signed build.
Regards
pinterest downloader

1. Check Cordova Plugins:

   • Verify that you have the necessary Cordova plugins installed and correctly configured for notifications. Popular plugins include "cordova-plugin-firebase" or "cordova-plugin-local-notifications."

2. Firebase Configuration:

   • If you are using Firebase Cloud Messaging (FCM) for notifications, ensure that your Firebase project is correctly configured, and you have the appropriate API keys and configuration files.

3. Background Services:

   • Notifications may not work in the background if your app for pc is using a service that is stopped by the Android system. Ensure that your app has a foreground service or a mechanism to handle background notifications.

When notifications are not working for a Cordova application in a 64-bit signed APK (Android Package), there could be several reasons for the issue. Here are some troubleshooting steps to help you identify Lil Uzi and potentially resolve the problem:

1. Check Permissions:

   • Verify that your Cordova application has the necessary permissions to send notifications. In the AndroidManifest.xml file, ensure that you have the <uses-permission> element for notifications:

Make sure you've correctly set up the sender ID, API key, and other configurations for your chosen push notification service. Updating all relevant Cordova plugins and dependencies to their latest versions is essential, as outdated components might not be compatible with 64-bit devices. Testing on various 64-bit Android devices can help identify whether the issue is device-specific. 
barcode font

If push notifications are not working for your Cordova application BloxEE when using a 64-bit signed APK, there could be several factors at play. Here are some steps you can take to troubleshoot and resolve the issue:

If notifications are not working in your Cordova application after building a 64-bit signed APK, there could be various reasons for the issue. Here are some general troubleshooting steps you can follow:

1. Check Permissions:

   • Ensure that your application has the necessary permissions to show notifications. In your AndroidManifest.xml file, make sure you have the <uses-permission android:name="android.permission.VIBRATE" /> permission.

2. Test on Different Devices:

   • Test your application for Alight motion on different devices running different Android versions. Some devices might handle notifications differently, and there might be specific issues on certain versions.

I enhanced our Cordova mobile application to accommodate 64-bit Android devices and incorporated Urban Airship (UA) for notifications. Unexpectedly, we are facing an issue where notifications are not received on the upgraded 64-bit version once it's signed. Interestingly, notifications are successfully delivered on both the 32-bit version (both signed and unsigned) and the 64-bit version when it remains unsigned.

XNXubd VPN Browser APK

This indicates that the notification infrastructure is operational, but there may be a specific configuration or setting affecting the 64-bit signed build.

Check Manifest Configuration: Ensure your app manifest file (AndroidManifest.xml) correctly requests notification permissions for 64-bit devices. You might need to add the android:usesCleartextTraffic="never" attribute to the <application> tag to comply with recent Android security changes on cleartext traffic.

Verify Signing Configuration: Double-check your signing configuration for the 64-bit APK. Make sure the keystore of id visa hub and key alias used for signing are correct and haven't been corrupted.
Rebuild Project: If there were any changes to the signing configuration, try rebuilding the entire project to ensure everything is integrated correctly.

Ensure that your 64-bit signed APK has correctly configured API keys, manifest settings, and signing certificates for notifications, and check for any specific configurations required by Urban Airship.

Double-check that your app has the necessary permissions to display notifications (e.g., android.permission.RECEIVE_BOOT_COMPLETED, android.permission.VIBRATE, android.permission.WAKE_LOCK).
Notification Channels: Ensure you've created notification channels in your app and configured them correctly.
UA Integration: Verify that the UA integration is set up correctly and that the necessary UA SDKs are included in your project.

Although my Qatar Visa Check has been configured correctly, but I'm unable to properly use it as well

Hi, We have rewritten this application in react native and hence this issue can be closed.

Hi, We have rewritten this application in react native and hence this issue can be closed.

Hi, We have rewritten this application in react native and hence this issue can be closed.

Good Post

• Google Services Configuration:
  Ensure that the google-services.json file (for Firebase) or any equivalent configuration for your notification service is correctly included in your project. Sometimes, misconfigurations can cause issues with signed builds.

• Signing Key Settings:
  Verify that the signing key used for the 64-bit APK is the same as the one registered in the notification service (e.g., Firebase Console or Urban Airship). Notifications won't work if the keys don't match.

• ProGuard/R8 Rules:
  If you’re using ProGuard or R8, check that the required classes and libraries for notifications are not being obfuscated or removed during the build process. Make sure the rules for the notification library (e.g., Urban Airship) are properly configured in your ProGuard file. You can also check your nol card balance quite easily at dubai metro line.

• Dependencies and Build Configuration:
  Ensure that all dependencies required for the notification service are properly included and updated for 64-bit compatibility. Also, check for any architecture-specific configurations.

• Urban Airship Settings:
  Double-check Urban Airship settings, especially the App Key and App Secret for the production environment. Ensure they are correctly configured and match the environment you're testing.

• Error Logs:
  Review the application logs when running the signed 64-bit APK. Look for any specific errors related to the notification service or initialization.

Cordova applications may face notification issues specifically in 64-bit signed APKs due to missing native libraries or incorrect plugin configurations. Ensuring all dependencies are compatible with 64-bit architecture is crucial. This often affects services like kuwait civil id payment where timely notifications are essential.