I ran into a problem that from time to time a picture in a OneSignal push notification does not come to the same device. This issue only reproduces on the android platform when the application is turned off. At first, the image may not come to the same device, then literally after 10 minutes it will come, while the device is connected to Wi-Fi and has a good connection speed. This issue only reproduces on the android platform when the application is turned off. At first, the image may not come to the same device, then literally after 10 minutes it will come, while the device is connected to Wi-Fi and has a good connection speed. The image weighs 56 kilobytes, has a resolution of 800 by 800 pixels in jpg format.
I use OneSignal v 3.5.0
Related
I have been using android studio device emulator to develop react-native apps and the emulator is taking upwards of 20 minutes to complete fetch requests (or any sort of data retrieval). When I build the same code on my physical phone the requests are completed instantly.
I have checked the device settings to make sure the network speed isn't everything seems ok there.
network speed set to full
The issue is persistent across my home desktop pc and my laptop and I have tried a few different system images.
Any help would be much appreciated!
My app entered the internal testing stage, meaning I upload it to Google Play Store as AAB bundle and then can install it on various devices.
I have noticed that the startup time of the app downloaded from the store is atrociously slow. The splash screen is hanging on for 10 - 15 seconds depending on the device.
On the other hand, if I install the very same app via USB from the dev machine it starts up instantaneously, with the splash screen visible for maximum 1 - 2 seconds.
Also, it looks like it is only the startup time that differs significantly. Regarding the overall performance of the app it is indistinguishable for the version installed via the USB cable and the one downloaded from the store.
I have absolutely no clue why this may be happening and will appreciate any suggestions pointing to what may be causing such behaviour.
I have set a timely notification of 30 minutes using JobScheduler, my app shows the notification in Android Emulator(Pixel 3 API 29 Q-10) after 30 minutes but not on my physical device(Samsung S8 Android 9 Pie).
The weird thing is the same notification shows up when I open the app after 30 minutes.
Are there any restrictions in android?
I have tried so far:
Running app in physical device using USB debugger mode, no errors.
Building the APK and installing it in the device separately
I found that, If the phone is in power saver mode or any battery optimized mode the notifications won't show up. Turning off power saver mode worked for me.
Everywhere I look I can only find questions about how slow the emulator is.
I'm running my app on a real android device. The app has several short animations and totals around 63MB storage. I understand that the more space the app uses the longer the installation will take, but it still takes 3 to 4 minutes to install and run every time.
I'm debugging through USB 2.0 and would expect far better transfer speeds.
I also tried copying a video from my android device to my computer (also via USB), which also took up about 60MB of space, and it took over a minute -- I seemed to get about 1MB/s upload speed.
Are these speeds expected, or should they be faster?
This morning my Samsung Galaxy Mega 6.3 (Android 4.4.2) rebooted suddenly. I was not doing anything at that time, and it was the very first time when it did that.
I managed to pull out a logcat using adb, but about 11 hours later. Also, I don't think that logcat was enabled on my phone at the time when the error occurred. Is there a way to see an error that is 12 hours long?
I suspect that the phone rebooted due to a system update. Is there a way to see a system update history, perhaps using an app instead of a code? I need the EXACT time (date + hour) of the last update.
Also, I don't think that logcat was enabled on my phone at the time when the error occurred
Logging is always enabled. LogCat simply reports what's in the log.
Is there a way to see an error that is 12 hours long?
The logging area is a ring buffer. It used to be fixed at 64KB. On Android 5.0, it is selectable by you via the Developer Options in the Settings app. I am not sure how big it is on Android 4.4 in general, let alone on a Samsung device.
How old the logs can be therefore is dependent on the size of the ring buffer and how much stuff gets logged. Unfortunately, production hardware logs a lot, so I would be skeptical that you can see 12+ hours back in the log. For example, on my Nexus 5, in a 256KB log buffer, I get about 8 hours of history.
Is there a way to see a system update history, perhaps using an app instead of a code?
Not that I am aware of, though that would be a better question for the Android Enthusiasts Stack Exchange.