[Bug]: Fail to Open Custom Sound File After Update APK

[yeekai18]

What happened?

I have two apk with different version. (Let's say 1.0.0 and 1.1.0)

After I install the app with 1.0.0 in Android device for the first time, the custom sound will trigger when notification is received. But after updating app with new version of apk 1.1.0, the custom sound does not trigger when notification is received.

I put the custom sound file in folder android/app/src/main/res/raw according to https://documentation.onesignal.com/docs/customize-notification-sounds#android-and-amazon. When I search for the output in Logcat, found out this line:

Failed to open file 'android.resource://com.mypackage.app/2131755013'. (No such file or directory)

If I uninstall the old app (1.0.0) and direct install the new one (1.1.0), or clear the data of the app (1.1.0), this will make a new subscription to OneSignal and now the custom sound will trigger again.

Have found similar issue reported here as well: OneSignal/OneSignal-Flutter-SDK#351

Steps to reproduce?

1. Install app for the first time and receive notification.
2. Custom sound will trigger in this case.
3. Update the app with another version of apk.
4. Custom sound does not trigger.

What did you expect to happen?

The custom sound will trigger when notification is received after update app without the need of uninstall or clear data.

React Native OneSignal SDK version

5.0.2

Which platform(s) are affected?

• iOS
• Android

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[jennantilla]

@yeekai18 just wanted to check in let you know that we are currently investigating this and will get back to you as soon as possible. Thanks!

[syahnurizal]

@jennantilla the issue still persist. Any solution yet?