Open fynngodau opened 3 years ago
@fynngodau I would enjoy seeing this implemented, especially for the emulator environment.
Perhaps it would be better for this wishlist item to be moved to the Android repository, since the error message is completely different on Android compared to the message on some versions of iOS?
Edit: Suggestive question above re-worded based on comments below about what happens on iOS.
Since it's a rather big suggestion with multiple different ideas, I imagined it would be a better fit for the wishlist repository. However if this is in fact better fit for the Android repository, somebody can of course feel free to move it there.
I think, you can't use the app on iOS 13-13.7 due to the lack of ENF v 2. So a discussion about this topic does also make sense for iOS, so the wishlist is the right place.
The main issue for the availability is: #443
@jucktnich / @Ein-Tim
What is the error message on iOS if ENF is not available? Does the app keep popping up an error message like on Android? https://www.coronawarn.app/en/faq/#17 is specific to Google/Android.
If the iOS version has no ENF v 2 there's an update os screen, which you can't close I think.
@MikeMcC399
The app shows:
You can't go any further from there
Ein-Tim Thank you very much for the iOS screen shot! That makes it clear. It seems like the problems on Android and iOS are quite different in that case.
Yes, I would also suggest to not mix the Android Error 3 pop up together with the availability on older devices, which is tracked in #443
I think the reason for the two messages are pretty much the same, so I would suggest to find a same solution for both.
Thanks for the comments. I added your additional points to the original comment to make the issue applicable to both iOS and Android.
@fynngodau and everyone else,
I have taken all your feedback and mirrored it to Jira as ticket EXPOSUREAPP-6594. The development team and the RKI will take a look at this.
Corona-Warn-App Open Source Team
@fynngodau and all - concerning Android: Isn't the pop up dialog triggered with every API call to ENS (causing an exception)? Imho, this is not so different from https://github.com/corona-warn-app/cwa-app-android/pull/2873 , the Bluetooth-based Incompatibility. Couldn't the exception be persisted and a Google Play Services Incompatibility card be shown? I think even the texts would only need minor adjustments. What do you think? (just to prevent misunderstandings: I don't mean changing the Bluetooth Incompatibility card, but adding another card for people affected) 2nd edit: @fynngodau already suggested this in his OP... 💤 😴
@fynngodau Actually you could another point in your OP: User might want to use the check-in feature.
@dsarkar
This is also tracked in #443.
@dsarkar This is already included under Expected benefits and in fact one of the main points why I opened this issue:
Users who are not using Google Play services can use Corona-Warn-App to check in at events and locations […]
(Though I forgot to update this to also apply to iOS)
@fynngodau You are right! Apologies, must have skipped it!
@fynngodau From your OP:
Suggested Enhancement
[...]
- Improve the flow. Integrate the warning with the information into onboarding, instead of allowing users to tap Enable Exposure Logging, then show a warning card on the home screen informing users of the status of the app.
That's now also in the mind of the devs: https://github.com/corona-warn-app/cwa-app-android/pull/2995#discussion_r622277201 ❤️
Let's hope there will be a more relaxed situation later, that there is enough time for them to go on on that issue.
@vaubaehn
Thanks for the pointer to PR https://github.com/corona-warn-app/cwa-app-android/pull/2995.
That is a good step forward. It could be made more user-friendly though if the app is going to be supported in future in an environment without Google Play services.
@vaubaehn Thanks for linking the PR, it appears to implements my suggestion number 2 for Android ("Pop up Android popup less").
Current Implementation
On devices without Google Play services, the Error 3 popup keeps popping up, annoying users. On iOS devices whose iOS version does not contain the required Exposure Notifications Framework version, the app is not usable at all.
Suggested Enhancement
In the order of work required (descending), and thereby also in the order of improvement of the app (ascending):
Expected Benefits
Internal Tracking-ID: EXPOSUREAPP-6594