u32i64: u32i64: I am afraid, but installing an older version from App Store is your mistake. Only App Store could improve this situation by saying UPDATE AND MAYBE LOSE YOUR DATA . You’ve been lucky and no database schema changes happened before this situation. When you install beta versions of any app, you agree that they may be unstable and you can lose your data. Testflight allows you to install any build that hasn’t expired (including downgrades) but you are responsible for not losing your data. Downgrades are just not supported. There is no DOWNGRADE button in the App Store.

All I wanted to do is to report a bug. Now I have to discuss with you.

You are, again, completely wrong.

Yes, there is no downgrade button in the app store, that is correct. But downgrading an app to an older version, and leaving a beta test to install the regular version again, are two different things.

In my language, I see the world “AKTUALISIEREN” in the app store, which is the german word for update/refresh. I click this button, when I want to install a new version of an app.

If I want to install an older version of an app, I cannot do so. this is correct.

If I want to leave the beta program for an app, the app store gives me directly the chance to do so. I see this app, let’s say Signal, on the top of the list in the app store, and I do not see the world “AKTUALISIEREN”, but “update”.

Since Apple is using a different word here, this proves, that the App Store knows very well, that you are using a beta version right now and would like to return to the normal version.

Clicking on update in the app store, while using a beta version, gives you the chance to return to the regular version - and this is intended by Apple.

Right now I’m testing 4 different betas. For all this procedure works.

For Signal it worked all the time back, for the last 2 years or so.

Now, with the new iOS beta 2.42, it is the first time at all, that I’ve experienced such a crash behavior, which is hopefully NOT intended and makes no sense.

So, is this a mistake of Apple’s App Store, or of Signal?

Of course I don’t know, but since I’ve seen this the first time, it is more likely a mistake of Signal.