App crash when I tried to open it

yandevelop / Bea

Lightweight BeReal. enhancement tweak.

123 stars 6 forks source link

App crash when I tried to open it #22

Open smule98 opened 1 year ago

smule98 commented 1 year ago

Hi I’ve:

iPhone 14 pro with iOS 16.6.1
BeReal. 1.13.0 installed
Bea 1.3.2 installed with sideoload When I try to open the app stays on the home screen with the BeReal logo for about 7/8 seconds and then crashes closing

yandevelop commented 1 year ago

I'm currently investigating this issue. I hope to fix it anytime soon. Will update this issue with information

TwentyFour-24 commented 1 year ago

Hey, as I'm having a jailbroken iPhone 6s and a sideloading 14 Pro and having tried out many combinations of sideloaded IPA and DEBs, I assume this is some sort of an issue with sideloaded IPAs. On the jailbroken device everything's fine. Felt for me, the issue started with the roll-out of BeReal 1.13.0 in the app store.

yandevelop commented 1 year ago

I'm starting to believe it's also some kind of BeReal's issue. See Post 1, Post 2

yandevelop commented 8 months ago

Hi, please test the latest release as I finally introduced some sort of fix that fixed the crashing problems for another user! https://github.com/yandevelop/Bea/releases/tag/1.3.6 Please report back if it works!

TwentyFour-24 commented 8 months ago

Hey, the new release works for me on sideloading. For some reason I had a 1.20.1 with Bea 1.3.3 working fine in the meantime. Thanks for your effords trying to fix it. ;)

yandevelop commented 8 months ago

Glad to hear that! Thanks for the feedback :)

smule98 commented 8 months ago

Hi my fried, yes now the app is loading but then I get this

yandevelop commented 8 months ago

Hi, thanks for reaching out. I was finally able to reproduce the issue. Here's a quick summary:

Depending on your sideloading service, the app's bundle id may get changed to something like: "AlexisBarreyat.BeReal.e718531" which is the cause of the issue that you cannot sign up ("An internal error has occurred..."
Basically the authentication server expects the bundle id to be the original one instead of the changed one from your side loading service and because of that the error occurs

This should be fixable from within Bea but I dont have that much time atm. I already looked into it but I couldn't find the appropriate methods to hook, so as a workaround you can try different side loading services that do NOT change the bundle id of the app that is to be side loaded. TrollStore for example doesnt change the app's bundle id and this is why I also never encountered this error.

MsieurASSE commented 8 months ago

I just tried with Sideloadly and I also get the error "An internal error has occurred..." but the bundle seems to be the original one.... So I don't understand 😅

yandevelop commented 7 months ago

Hmm yes that is weird. Without more information on what the "internal error" is I don't know what causes the issue for you. I can only try to fix this based what I am currently aware of what the issue could be

Ein-Tim commented 7 months ago

I have the same issue as @MsieurASSE.