ok so I know for Android you have to put the custom sound for a push notification in the res/raw folder, and this worked for me once a while back. But now when I create the folder /raw in my root (which I thought was the resources directory… or at least it used to be at one time) It puts my raw folder in the /assets folder once I build for Android. Why you do that 
Corona expects the audio file to be kept with the rest of your Corona project files, which in the post-build step gets copied to the APK’s assets directory. That is, Corona does not look for you audio file under your project’s “res” directory.
Have a look at sample project “System/GooglePushNotifications” that comes with the Corona Simulator. You want to add a custom/embedded notification WAV file as shown in that example, which *does* work for Corona Enterprise as well. In particular, look at the “main.lua” file’s onTap() function. The important detail there is that the JSON needs to reference that audio file via the JSON’s “data.sound” field.
I did fail to mention I was trying this with OneSignal. Their SDK does require it be in res/raw folder.
The odd thing is I had this working with a custom sound on OneSignal not too long ago. Then I rebuilt with newest build and no custom sound anymore.
Well, then I’m not sure how this can be a problem on our end. There’s nothing to stop you from putting your audio file under your Android application project’s “res/raw” directory. Just make sure to put it under your Android application project directory, *not* in the Corona project directory, which gets copied to “assets”.
Do I just create a folder called Android? How do I put it in the android application project directory? Is that an Enterprise feature?
Perhaps I’m misunderstanding what you’re doing.
​Are you do a build via the Corona Simulator or Corona Enterprise?
(I’ve been assuming that you were talking about Corona Enterprise the whole time.)
If you’re doing a Corona Simulator build, then right, you have no means of adding files to the Android “res” directory. You’d have to check OneSignal’s documentation about what your other options might be.
Unfortunately my enterprise license expired so now I’m just building via simulator. Was thinking maybe I could decompile, move file to folder and recompile resign zipalign… I wonder if that would work?
I just looked at OneSignal’s documentation (link below). You’re right. They don’t support custom notification sounds on Android with Corona Simulator built apps. This is currently only possible with Corona Enterprise users.
  https://documentation.onesignal.com/v2.0/docs/corona-sdk-installation#custom-notification-sounds-ios
Corona expects the audio file to be kept with the rest of your Corona project files, which in the post-build step gets copied to the APK’s assets directory. That is, Corona does not look for you audio file under your project’s “res” directory.
Have a look at sample project “System/GooglePushNotifications” that comes with the Corona Simulator. You want to add a custom/embedded notification WAV file as shown in that example, which *does* work for Corona Enterprise as well. In particular, look at the “main.lua” file’s onTap() function. The important detail there is that the JSON needs to reference that audio file via the JSON’s “data.sound” field.
I did fail to mention I was trying this with OneSignal. Their SDK does require it be in res/raw folder.
The odd thing is I had this working with a custom sound on OneSignal not too long ago. Then I rebuilt with newest build and no custom sound anymore.
Well, then I’m not sure how this can be a problem on our end. There’s nothing to stop you from putting your audio file under your Android application project’s “res/raw” directory. Just make sure to put it under your Android application project directory, *not* in the Corona project directory, which gets copied to “assets”.
Do I just create a folder called Android? How do I put it in the android application project directory? Is that an Enterprise feature?
Perhaps I’m misunderstanding what you’re doing.
​Are you do a build via the Corona Simulator or Corona Enterprise?
(I’ve been assuming that you were talking about Corona Enterprise the whole time.)
If you’re doing a Corona Simulator build, then right, you have no means of adding files to the Android “res” directory. You’d have to check OneSignal’s documentation about what your other options might be.
Unfortunately my enterprise license expired so now I’m just building via simulator. Was thinking maybe I could decompile, move file to folder and recompile resign zipalign… I wonder if that would work?
I just looked at OneSignal’s documentation (link below). You’re right. They don’t support custom notification sounds on Android with Corona Simulator built apps. This is currently only possible with Corona Enterprise users.
  https://documentation.onesignal.com/v2.0/docs/corona-sdk-installation#custom-notification-sounds-ios