Can’t login

[sergue22]

Keep getting this when I enter the otp. The code is definitely right.

[andybaws]

I have the same problem, it works with the original app, but with Befake not.

[yandevelop]

I don't know what's wrong there. Bea does not inject any code into anything related to logging in. Will try to figure it out but I currently don't know where to start lol

[TwentyFour-24]

@sergue22 Are you sideloading Bea?

If so, I'm sure it's linked to issues #21 and #22 with generally refusing any server connection to sideloaded versions. Sideloading the original IPA, verifying the code, then sideload Bea to the same BundleIdentifier solved this. But then you're prolly facing the above linked issue being stuck in loading screen.

[yandevelop]

So you actually got it working now? What do you mean by "verifying the code"?

[TwentyFour-24]

1) Sideloading BeReal IPA with BundleIdentifier e.g. "AlexisBarreyat.BeReal2" 2) Recieving SMS code 3) Entering it and it works (ofc without Bea) 4) Sideloading Bea IPA with same BundleIdentifier, installing over. 5) Bea is starting, but stuck in loading screen as issue #21. The verification stays valid.

[yandevelop]

Ok, I think you could also do the SMS verification without the changed bundle id and instead just download BeReal from the app store.

[TwentyFour-24]

Ok, I think you could also do the SMS verification without the changed bundle id and instead just download BeReal from the app store.

True, I'm using the 2nd Identifier to have both apps installed, BeReal and BeFake ;) Just wanted to emphasise that the ID needs to be the same, to keep the verification working...

[yandevelop]

I've attempted to reproduce the issue. I've got 2 test devices and everything works fine on both. Sideloaded normal BeReal, and BeReal with Bea injected. It never crashed. Please test: https://easyupload.io/u1rju0. This is BeReal 1.13 with Bea 1.3.2 injected.

[andybaws]

I sideloaded original bereal and after that I installed befake 1.12.0 and now it works.

[Xanderman27]

I receive the same error

[Bernarduzz]

How do I sideload original bereal? The Bea with 1.3.2 injected into BeReal 1.13 still doesnt work for me.

I've attempted to reproduce the issue. I've got 2 test devices and everything works fine on both. Sideloaded normal BeReal, and BeReal with Bea injected. It never crashed. Please test: https://easyupload.io/u1rju0. This is BeReal 1.13 with Bea 1.3.2 injected.

[yandevelop]

Get decrypted IPA online and then sideload

[mystrd]

Not working for me. Have original bereal installed from appstore and have installed the easyupload version of 1.13 with Bea 1.3.2 in your post. It installs but crashes on loading. Don't even make it as far as the SMS verification screen.

[gando08]

How do I sideload original bereal? The Bea with 1.3.2 injected into BeReal 1.13 still doesnt work for me.

I've attempted to reproduce the issue. I've got 2 test devices and everything works fine on both. Sideloaded normal BeReal, and BeReal with Bea injected. It never crashed. Please test: https://easyupload.io/u1rju0. This is BeReal 1.13 with Bea 1.3.2 injected.

Bernarduzz tell me if the procedure works for you. So in case I try to run it as well

[Bernarduzz]

Nope, even sideloading the BeReal doesnt work for me. It was kind of strange when I reinstalled into the AppStore BeReal since it directly log me in without any verification. Not sure if it was supposed to be that way

How do I sideload original bereal? The Bea with 1.3.2 injected into BeReal 1.13 still doesnt work for me.

I've attempted to reproduce the issue. I've got 2 test devices and everything works fine on both. Sideloaded normal BeReal, and BeReal with Bea injected. It never crashed. Please test: https://easyupload.io/u1rju0. This is BeReal 1.13 with Bea 1.3.2 injected.

Bernarduzz tell me if the procedure works for you. So in case I try to run it as well

[gando08]

Nope, even sideloading the BeReal doesnt work for me. It was kind of strange when I reinstalled into the AppStore BeReal since it directly log me in without any verification. Not sure if it was supposed to be that way

How do I sideload original bereal? The Bea with 1.3.2 injected into BeReal 1.13 still doesnt work for me.

I've attempted to reproduce the issue. I've got 2 test devices and everything works fine on both. Sideloaded normal BeReal, and BeReal with Bea injected. It never crashed. Please test: https://easyupload.io/u1rju0. This is BeReal 1.13 with Bea 1.3.2 injected.

Bernarduzz tell me if the procedure works for you. So in case I try to run it as well

Okay thanks for the feedback. Then I guess the crash is due to the new substantial update made last week

[Bernarduzz]

Anybody have any update on any other method that works?

[gando08]

I think we have to start to post real photo😂

[yandevelop]

I can try and inject Bea into BeReal 1.14 if anyone wants to test it

[Bernarduzz]

Maybe someone could guide me over here and see if I did anything wrong in the process.

So I tried sideloading decrypted BeReal for both 1.13 and 1.12 and I never got pass the text verification. It was always bad communication or wrong code. I was using sideloadly with automatic bundle ID and apple ID sideload. I don't see any reason why it verify text mesage for sideloading normal BeReal.

I have tried both injecting and Bea, no luck so far in sign in. I did try to reset every couple times it errors in the advanced setting just to see if it does anything.

I can try and inject Bea into BeReal 1.14 if anyone wants to test it

[gando08]

I can try and inject Bea into BeReal 1.14 if anyone wants to test it

I can test it

[TwentyFour-24]

I can try and inject Bea into BeReal 1.14 if anyone wants to test it

In 1.13 and 1.14 the download button and the "BeFake" text (clicking the empty space still opens the posting menu) is gone for me again. :) But I don't know how, but when trying today, I made it past the verifying point and everything is working. (in both installed app "BeReal." and "BeFake."

[MsieurASSE]

Hello, few days ago my BeFake app wasn't refreshing anymore the app content so I tried to disconnect my account and reconnect to restart the process with the server and try to make the app working again. Result : I can't connect to my account on BeFake anymore. I tried everything: different versions of BeReal IPA with the BeFake tweak, basic version without the BeFake tweak (decrypted basic IPA). In conclusion, it seems to be impossible to connect an account to a sideloaded BeReal, even if that is the appstore version... :(

[gando08]

I can try and inject Bea into BeReal 1.14 if anyone wants to test it

In 1.13 and 1.14 the download button and the "BeFake" text (clicking the empty space still opens the posting menu) is gone for me again. :) But I don't know how, but when trying today, I made it past the verifying point and everything is working. (in both installed app "BeReal." and "BeFake."

So are you saying it's working befake again? Can you describe step by step the procedure you performed?

[gando08]

any news from TwentyFour-24 or yandevelop?

[MsieurASSE]

Up! The problem still persists...

[yandevelop]

See https://www.reddit.com/r/bereal_app/s/r8F3tOba3d and various other posts on r/bereal_app. That is a server side issue and there's nothing i can do to fix this. Bea does not cause this issue. BeReal is struggling with authentication since forever. Please contact BeReal support

[yandevelop]

I just uploaded the latest BeReal (1.16) with Bea injected: Releases - Please try if that fixes any of the issues listed here.

[gando08]

I just uploaded the latest BeReal (1.16) with Bea injected: Releases - Please try if that fixes any of the issues listed here.

still not working

[yandevelop]

Ok. I have no clue why that is and again I can't think of anything that Bea injects into that would trigger this issue. Please reach out to BeReal support

[itsnotrin]

I just sideloaded and it's working perfectly, I made a new account and it asked for the SMS code and it just worked perfectly fine. I sideloaded using E-Sign on ios 16.6B1, dev certificate.

[gando08]

I get stuck loading the app and then it crashes. So I can't even make a new account. Can you provide more information on how you managed to install it? Also what iphone did you use and what version of IOS does it have?

[itsnotrin]

Apologies for the late reply.

iPhone xR, iOS 16.6B1, Installed using an apple developer cert, purchased from MapleSign, installed using E-Sign.

[yandevelop]

Hi, please test the latest release https://github.com/yandevelop/Bea/releases/tag/1.3.6 Let me know if this fixes the issues!

[h4rqq]

Hi, please test the latest release https://github.com/yandevelop/Bea/releases/tag/1.3.6

Let me know if this fixes the issues!

I doesn't work with the last update and even with the remove mobileprovition option on ESign. Maybe it depends on the side loading method?

[Ein-Tim]

I just tried to log in, but I'm getting an error message. Maybe this is related to https://github.com/rvaidun/befake/issues/199?

[h4rqq]

Which error message are you getting? Were you able to log in until yesterday?

[Ein-Tim]

I just tried using Bea today, so I can't comment on the situation in the past. I'm getting this screen:

[h4rqq]

Seems like they enforced a signature. Reverse engineering is needed for BeReal viewers to work. Bruh this might be the end of BeReal viewers app/web

[h4rqq]

The only thing we got now is to wait to see if someone manages to reverse engineering it

[Ein-Tim]

I guess that's the end, as this could quickly become a cat and mouse game, in which the open source community reverse engineers the signature, the apps briefly work, BeReal changes the signature, and so on...

[h4rqq]

We were already playing at that game since months ago but they finally caught us. Also if someone actually manages to find a work around it will be better for them not to share it

[yandevelop]

Well, in theory, the "bereal-signature" in the headers was already present for a long time. Unblurring in Bea doesn't depend on any API calls since this is done on device and should work without any errors atm. For posting a BeFake from within Bea I have no reports of it not working. Also, the sign up process should not be affected by this change, since this is done natively and Bea doesnt intercept anything. The screenshot @Ein-Tim posted is a known error and was also referenced here: https://github.com/yandevelop/Bea/issues/22#issuecomment-1933670244. Please try a different signing service such as Sideloadly or TrollStore to install the IPA and try if this fixes the issue.

[Ein-Tim]

@yandevelop I tried with sideloadly but I'm still getting the same issue:

[yandevelop]

Can you tell me what the bundle ID is?

[Ein-Tim]

@yandevelop I just checked and can confirm that Sideloadly changed the BundleID to "AlexisBarreyat.BeReal.99HY2TS5L8" while the offical app has the BundleID "AlexisBarreyat.BeReal"

[Ein-Tim]

@yandevelop I tried to manually change the bundle ID to "AlexisBarreyat.BeReal" in the Sideloadly advanced settings, but I can't confirm whether this is working or not as I now received the error: "Your maximum App ID limit has been reached. You may create up to 10 App IDs every 7 days."

So I guess I have to wait 7 days and re-check then.

[yandevelop]

I guess so, idk much about sideloading either. You can try using a different apple ID. If you are on a supported version, I recommend installing the app through TrollStore. Yes, if the bundle id gets changed to something like that, the error you posted above occurs. Currently having exams, but in approx 2 weeks I will have lots of time to try and fix it.

[Ein-Tim]

Thank you @yandevelop! Good luck at your exams!

[h4rqq]

Well, in theory, the "bereal-signature" in the headers was already present for a long time. Unblurring in Bea doesn't depend on any API calls since this is done on device and should work without any errors atm. For posting a BeFake from within Bea I have no reports of it not working. Also, the sign up process should not be affected by this change, since this is done natively and Bea doesnt intercept anything. The screenshot @Ein-Tim posted is a known error and was also referenced here: https://github.com/yandevelop/Bea/issues/22#issuecomment-1933670244. Please try a different signing service such as Sideloadly or TrollStore to install the IPA and try if this fixes the issue.

Strange, I've tried using Sideloadly but it doesn't works. Now I know it's not a bea problem because I tried to sideload a clean BeReal IPA and I got the same error. Maybe sideloaders are changing some things when installing? Idk