-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[question]: Notification Images Not Showing in Battery-Saver mode #1665
Comments
@appverkdev Thanks for the question. Battery-Saver mode varies quite a bit between Android versions and device manufactures. Normally the only side effect of enabling this is delayed notifications. Can you list the Android versions and device models you have tested and noticed this issue with? Also list the steps you took to enable the battery mode to ensure we are comparing the same setting too. Also, did you have Data Saver on with Battery Saver in your testing? If so, was it on WiFi or cell data? |
Hi, sorry for the late response. Issue happens in any battery saver mode on: Wifi and cell data as well. |
@appverkdev Thanks for the details, could you capture the full logcat from the device for both these scenarios so it can be compared? Send a notification with an image:
You can share these here as attachments to your Github reply, or if you wish to keep the log private share with OneSignal support and link them to this thread. |
Closing issue due to no response. Please @ mention me if we need to revisit. We have an updated major release available for our Android SDK with many improvements and enhancements! Please refer to the migration guide for more information on upgrading. Thanks! |
How can we help?
Hi,
I was wondering if the OneSignal SDK has any solution to loading images in Battery-Saver mode, other than the one mentioned in troubleshooting (hosting photos on OneSignal/Image size changing)? I am encountering this problem in every library I try to use and am trying to find the one without it.
Thanks!
Code of Conduct
The text was updated successfully, but these errors were encountered: