Test a new version as beta in the community

[HeiDasGri]

Current Implementation

new versions are distributed to all users at the same time. Possible errors are identified quickly, but then also affect inexperienced users

Suggested Enhancement

Provide a new version as a kind of public beta. It would be great, when someone without a developer account could use it.

Expected Benefits

If it were possible to make this version available to the community one to two days in advance, problems could be identified in good time without a bad headline in the press. See corona-warn-app/cwa-app-ios#1037 as an example here.

---

Internal Tracking ID: EXPOSUREAPP-2840

[melloskitten]

Hi @HeiDasGri
Thank you very much for your proposal. I will address this with the responsibles for our process.
Cheers! 👍

[ghost]

This might be related to corona-warn-app/cwa-app-ios#999 regarding community testing.

[PalminX]

I think for iOS, it would make sense to open up Testflight pre-release builds for interested members of the community

[Jens07]

I think the failure in corona-warn-app/cwa-app-ios#1037 is the best argument to implement this proposal. We could avoid so much bad publicity.

[kbobrowski]

Pre-release builds on Android are already being tested by community using this project: https://github.com/kbobrowski/en-i13n , extension for iOS should also be possible, but it would require someone with jailbroken device to develop it

[PalminX]

Pre-release builds on Android are already being tested by community using this project: https://github.com/kbobrowski/en-i13n , extension for iOS should also be possible, but it would require someone with jailbroken device to develop it

I don't think that this is necessary nor feasible on iOS. Having pre-release access through Apple TestFlight is the normal way, and it is accessible to everyone (by invitation). Jailbroken iOS devices are not really common, and this would target the wrong user base.

[gusowski1]

For google there is to the posibility to use internal testgroups, closed testgroups and open testgroups via the playservices without the need for rooted devices.
https://support.google.com/googleplay/android-developer/answer/3131213?hl=de

[ndegendogo]

As @PalminX already mentioned. Apple provides an environment for beta testing iOS apps.

https://developer.apple.com/testflight/

Assuming you are already in close discussion with Apple, I would suggest, that you get confirmation whether there are any limitations with regard to the special entitlement required for the ENF.

[PalminX]

As far as I can see Testflight is already used, it's just a matter of opening to a wider audience.

[kbobrowski]

This would be great if pre-release was available via Play Store / Testflight, but community testing was already requested 3 months ago and we still don't have it: corona-warn-app/cwa-documentation#214. SAP cannot do much about it since RKI is responsible for distributing the apps, and I guess this feature request was already communicated there. Perhaps someone could update us on what is the current RKI opinion on community testing :)

[mtb77]

@kbobrowski I will bring up this question to the RKI next week and will give you an update.
For Android we have discussed to attach test-apks on certain bug tickets, so the reporter can test against our fix. We can not guarantee that for every bug / every pull-request, but at least on tickets that are hard to trace we will try this approach.
On iOS this option is not possible as of the need to have the app signed by a developer certificate and either use an enterprise certificate or whitelist the UUID of the device in the provisioning profile.
In the meantime an iOS developer can of course pick the pull request and build / sign it with his own signature on his own device.

Cheers,

Sascha
Corona-Warn-App Open Source Team

[ndegendogo]

In the meantime an iOS developer can of course pick the pull request and build / sign it with his own signature on his own device.

Is this really sufficient? As to my understanding, this will be missing the entitlement for EN Framework - or is there a misunderstanding on my side?

[mtb77]

@ndegendogo No you are right, to get the entitlement from Apple it need to be requested (https://developer.apple.com/contact/request/exposure-notification-entitlement), so the local testing options are limited.
According to the guidelines https://developer.apple.com/contact/request/download/Exposure_Notification_Addendum.pdf even accessing EN FW is prohibited.

You acknowledge and agree that You will not access, or attempt to access, the Exposure Notification APIs unless You have received an Entitlement Profile from Apple

Cheers,

Sascha
Corona-Warn-App Open Source Team

[cfritzsche]

I think on iOS, RKI would have to open up TestFlight to outside beta testers to allow this..

[Ein-Tim]

And another good reason to implement this: corona-warn-app/cwa-app-ios#1497

[ndegendogo]

Definitely.

A friend of mine is proud owner of the newest iPhone since Tuesday, and has eagerly installed cwa 1.5.3(0). His previous iPhone had not been supported.
So, yesterday he saw the new version 1.6.0, happily updated, wanted to start it, and -bang!!
You can bet he was pissed-off ...

[Ein-Tim]

Is there any chance we will See a Beta of the new 1.7.0 release to see if it's working properly? With so many files changed and the more frequent risk update I think this would be good...

I also have a specific question, @d4rken stated here in the Community Slack, that Version 1.6.1 has been stage-rollouted under Android.
@mtb77 Is something similar also planed for iOS? (is this even possible? 😅)

[ouboub]

And another reason for beta tests: corona-warn-app/cwa-app-ios#1715 (only something minor - but still irritating for the normal user)

In my understanding the next release will be 1.10, including a contact diary.
This is another reason to have more beta testers, the current implementation as one can see in pull request
corona-warn-app/cwa-app-ios#1695 (comment)
does not include certain features, as
send warning for each user individually.

[dsarkar]

Dear community,

this topic is discussed internally. I hopefully can come back with some updates soon. DS

---

Corona-Warn-App Open Source Team

[ouboub]

>> "d" == dsarkar ***@***.***> writes: Dear community, this topic is discussed internally. I hopefully can come back with some updates soon. DS

Thanks

[2x-pr0]

chip.de was able to test the upcoming feature ... “contact diary”

[ouboub]

>> "2" == 2x-pr0 ***@***.***> writes:  chip.de was able to test the upcoming feature ... “contact diary”

Hm, I don't want to comment on the fact that a journal, even a journal that popular as chip, has access to a beta version, but people outside the developer circle have not,.... But I cannot find the information on the link you provided. Could you please try to give a more specific link? Thanks

[Ein-Tim]

I assume (and after watching the video in the article I'm quite sure) that chip simply build the App via XCode/an emulator (how it's described for iOS here and for Android here).

@ouboub Here is the link to the article: https://www.chip.de/news/Grosse-Aenderungen-geplant-So-sieht-die-Corona-Warn-App-bald-aus_183190218.html

[MikeMcC399]

@Ein-Tim

I assume (and after watching the video in the article I'm quite sure) that chip simply build the App via XCode/an emulator (how it's described for iOS here and for Android here).

I can confirm that you can do that. For Android, you need Android Studio, fetch the repo, checkout the release/1.10.x with git, build it, then run it on an Android 11 Pixel emulator. You just need to dismiss the error message which comes up several times because the app isn't signed, so it can't access the Google Exposure Notification System.

The contact diary looks like the chip.de screen shots. You can define People and Places, which you can then add to a day of your diary.

[ouboub]

>> "ET" == Ein Tim ***@***.***> writes: That chip tested it does not mean that they've got their hands on a beta,the could've simply build the App via an Emulator (how it's described for iOS

Ok that makes some sense.

…

[here](https://github.com/corona-warn-app/cwa-app-ios/blob/release/1.11.x/README.md#development) and for Android [here](https://github.com/corona-warn-app/cwa-app-android/blob/release/1.11.x/README.md#development)).

[ouboub]

>> "MM" == Mike McCready ***@***.***> writes: @Ein-Tim > I assume (and after watching the video in the article I'm quite sure) that chip simply build the App via XCode/an emulator (how it's described for iOS here and for Android here).

Which video? Can you please provide a link.

I can confirm that you can do that. For Android, you need Android Studio, fetch the repo, checkout the release/1.10.x with git, build it, then run it on an Android 11 Pixel emulator. You just need to dismiss the error message which comes up several times because the app isn't signed, so it can't access the Google Exposure Notification System. The contact diary looks like the chip.de screen shots. You can define People and Places, which you can then add to a day of your diary.

I still can't find that article, any pointers please?

[Ein-Tim]

@ouboub Here is the link (again): https://www.chip.de/news/Grosse-Aenderungen-geplant-So-sieht-die-Corona-Warn-App-bald-aus_183190218.html. In this article you'll also find the video.

[ouboub]

>> "MM" == Mike McCready ***@***.***> writes: @Ein-Tim > I assume (and after watching the video in the article I'm quite sure) that chip simply build the App via XCode/an emulator (how it's described for iOS here and for Android here). I can confirm that you can do that. For Android, you need Android Studio, fetch the repo, checkout the release/1.10.x with git, build it, then run it on an Android 11 Pixel emulator. You just need to dismiss the error message which comes up several times because the app isn't signed, so it can't access the Google Exposure Notification System. The contact diary looks like the chip.de screen shots. You can define People and Places, which you can then add to a day of your diary.

This is the link? https://www.chip.de/news/Grosse-Aenderungen-geplant-So-sieht-die-Corona-Warn-App-bald-aus_183190218.html

[ouboub]

>> "ET" == Ein Tim ***@***.***> writes: @ouboub Here is the link (again): https://www.chip.de/news/Grosse-Aenderungen-geplant-So-sieht-die-Corona-Warn-App-bald-aus_183190218.html. In this article you'll also find the video.

Thanks, the export function is not described, in my eyes, as I said several times, the weak point of the new functionality. It does not respect the privacy, since you cannot export single meetings only all-or-nothing.

[Ein-Tim]

@thomasaugsten stated 1 month ago in the iOS repository:

The public beta is already addressed and will be decided soon

Is there any update about public beta versions (i.e. iOS Testflight)?

[thomasaugsten]

There is no update at the moment this is not possible

[jucktnich]

Small question: What's the problem about the TestFlight app? Is there any restriction with ENF?
I think version 2.2 showed, how important a TestFlight beta would be, since I found 2.5 bugs in under 10min