fix: android intent-filter generation for packages with uppercase letters

[subhankarmaiti]

When an Android application package name contains uppercase letters (e.g., com.testApp), the auto-generated intent-filter in the AndroidManifest file uses the original casing in the pathPrefix attribute. However, the callback URI generation already lowercases the bundle identifier, causing a mismatch that prevents the app from properly handling the Auth0 callback after authentication.

Solution

This PR lowercases the applicationId in the Expo config plugin before using it to generate the Android intent-filter, ensuring consistency with the callback URI generation logic.

Changed:

• src/plugin/withAuth0.ts: Modified withAndroidAuth0Manifest to lowercase the package name via config.android?.package?.toLowerCase()

This aligns with the existing behavior in NativeWebAuthProvider.ts where the bundleId is lowercased when generating callback URIs.

Impact

• Developers using package names with uppercase letters will no longer need to manually modify their AndroidManifest.xml
• The intent-filter's pathPrefix will now consistently use lowercase package names, matching the callback URL structure
• No breaking changes for existing apps with lowercase package names

Testing

• Verify that apps with uppercase package names (e.g., com.testApp) can successfully authenticate and receive callbacks
• Confirm existing apps with lowercase package names continue to work as expected
• Test with custom schemes to ensure compatibility

References

• Issue: on the Android side, How to open the login page normally when the application package name contains uppercase letters  #877
• Related comment: on the Android side, How to open the login page normally when the application package name contains uppercase letters  #877 (comment)