Tyler Roach

Hi @yaroslav-v, please upgrade to Amplify 1.36.5. After releasing 1.36.4 on July 26, we observed the crash internally and through a customer report on July 27. We released a hotfix...

@cmllamosas Are you seeing this in a release, or possibly debugging with breakpoints? The Android OS has a requirement that when `startForegroundService()` is called, `startForeground()` must be called within the...

@cmllamosas Thank you, again, for your prompt response! - What targetSdkVersion is the app using? - Where are you starting the upload process? (Ex: Activity, Service)? - Are you seeing...

@yaroslav-v Thank you for the provided details. From the 1.36.4 release, to the 1.36.5 release, we made a change that we are confident should reduce the instances of this crash....

@cmllamosas In the image you attached, please select the "3-dot" icon on the top right. You should then have a menu item to click for "All permissions". Please report back...

@cmllamosas I see that you have "run foreground service" permission so that speculated cause is not the issue. Earlier you had responded that the crash happens 100% of the time....

Editing this message, sorry for the confusion. I thought that I could replicate this error by providing a download with a non-existent key, however, I had left in a line...

@cmllamosas Downloaded. I'll folllow-up after review.

@cmllamosas I can see 2 instances where TransferService is being moved to the foreground and then stopped. A pdf download and a failed image download. If there were any more...

@yaroslav-v Thank you for the update. I believe you may be running into a scenario where `startForegroundService` is called on the TransferService. This should trigger `TransferService.onStartCommand`, which calls the required...