Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

Prioritized background activity, cause 10 appears after switch #981

Closed
3 tasks done
SebastianWolf-SAP opened this issue Aug 6, 2020 · 8 comments
Closed
3 tasks done
Assignees
Labels
bug Something isn't working mirrored-to-jira This item is also tracked internally in JIRA

Comments

@SebastianWolf-SAP
Copy link
Member

SebastianWolf-SAP commented Aug 6, 2020

Avoid duplicates

  • Bug is not mentioned in the FAQ
  • Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
  • Bug is not already reported in another issue

Describe the bug

Report from hotline:
The user of the app clicks on settings and wants to enable the prioritized background activity.
Instead of the successful enabling of the feature the user receives the error message: "Ursache 10 irgendwas ist schiefgelaufen, diese Aktion ist leider aktuell nicht verfügbar. Bitte kontaktieren sie die technische Hotline" (engl: Cause 10 something went wrong, the action is currently not available. Please contact the technical hotline")

Expected behaviour

See above

Technical details

  • Mobile device: Samsung A5 2015
  • Android version: 6.0.1

In case you see this behavior as well, please comment underneath mentioning your device and Android version. Thanks!


Internal tracking ID: EXPOSUREAPP-2022

@SebastianWolf-SAP SebastianWolf-SAP added bug Something isn't working mirrored-to-jira This item is also tracked internally in JIRA labels Aug 6, 2020
@m122-gh
Copy link

m122-gh commented Aug 14, 2020

Hallo Herr Wolf,
Ich habe ein Samsung S5duos (G900FD) mit Android 6.0.1 und genau das beschriebene Problem.
Wie kann ich das beheben??

@PhilippNowak96
Copy link
Contributor

This sounds like the problem described here: https://stackoverflow.com/questions/44862176/request-ignore-battery-optimizations-how-to-do-it-right/50840603#50840603. Unfortunately I have no Samsung running Android 6 to test this myself but maybe you guys can try to have a further look based on this information.

@vaubaehn
Copy link
Contributor

This sounds like the problem described here: https://stackoverflow.com/questions/44862176/request-ignore-battery-optimizations-how-to-do-it-right/50840603#50840603. Unfortunately I have no Samsung running Android 6 to test this myself but maybe you guys can try to have a further look based on this information.

@PhilippNowak96 looks like a good find!
Pushing forward to @svengabr

@svengabr
Copy link
Member

When taking a look at the Jira tickets, this issue might be resolved with 1.3.0. Could you check again if the error still persists in the latest version?

EXPOSUREAPP-1885

Cheers

@vaubaehn
Copy link
Contributor

vaubaehn commented Sep 10, 2020

hi @svengabr ,

When taking a look at the Jira tickets, this issue might be resolved with 1.3.0. Could you check again if the error still persists in the latest version?

EXPOSUREAPP-1885

just to prevent any confusion, and for double checking: this issue here is about CAUSE 10 (android.content.ActivityNotFoundException) - and obviously has more rare effects specifically on Samsung devices running Android 6. The link provided by @PhilippNowak96 https://stackoverflow.com/questions/44862176/request-ignore-battery-optimizations-how-to-do-it-right/50840603#50840603 seems to be rather useful. So, it's not about API 10...
Also, I couldn't find any related PR for 1.3.0 nor for 1.3.1 RC1.

Thanks for checking :)

I also double checked: PR #1116 might have an effect (EXPOSUREAPP-2506) here, but can't understand for which release it's planned.

@svengabr
Copy link
Member

Hey @vaubaehn

I just checked again today for the ticket I mentioned (EXPOSUREAPP-1885) and it was reopened yesterday by the development team. Internal the ticket was mentioned to be related this is why i thought it could already been fixed.

Hi everyone, I have reopened this issue, since there is no background activity on the Xiaomi devices despite Google's watchdog as long as MIUI energymode is on (by default). BR Katharina

I just corrected the assignee here and gave it to @harambasicluka since he is working on the original Jira issue currently.

Best regards,
SG

Corona-Warn-App Open Source Team

@heinezen
Copy link
Member

Hello everyone,

This issue was addressed in CWA version 1.6 and should be fixed by now. Please check if the bug was fixed for you.

CH


Corona-Warn-App Open Source Team

@heinezen
Copy link
Member

Since we had no more reports for a month, this is considered to be fixed.


Corona-Warn-App Open Source Team

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working mirrored-to-jira This item is also tracked internally in JIRA
Projects
None yet
Development

No branches or pull requests

8 participants