Can’t login #24
Comments
|
I have the same problem, it works with the original app, but with Befake not. |
|
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 |
|
@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. |
|
So you actually got it working now? What do you mean by "verifying the code"? |
|
|
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 ;) |
|
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. |
|
I sideloaded original bereal and after that I installed befake 1.12.0 and now it works. |
|
I receive the same error |
|
How do I sideload original bereal? The Bea with 1.3.2 injected into BeReal 1.13 still doesnt work for me.
|
|
Get decrypted IPA online and then sideload |
|
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. |
Bernarduzz tell me if the procedure works for you. So in case I try to run it as well |
|
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
|
Okay thanks for the feedback. Then I guess the crash is due to the new substantial update made last week |
|
Anybody have any update on any other method that works? |
|
I think we have to start to post real photo😂 |
|
I can try and inject Bea into BeReal 1.14 if anyone wants to test it |
|
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 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. :) |
|
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... :( |
So are you saying it's working befake again? Can you describe step by step the procedure you performed? |
|
any news from TwentyFour-24 or yandevelop? |
|
Up! The problem still persists... |
|
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. |
|
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 |
|
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 |
|
Here I am with a quick update, prob the issue has nothing to do with the bundle id, I changed bereal's bID to see how it would behave and found out that if bID is changed you will get error "Bad request (400)" this means that bea sideloads with the original bID and that the problem seems not to be the sideloading method. I will use my pc to search for bea and bereals bID and see what's wrong |
|
Bea's bundle id is "com.yan.bea" but that doesnt matter anyways. I looked at the errors in Console and literally Firebase authentication said that the bundle ids don't match. So that is why i made this assumption in the first place. I also intercepted the traffic made from BeReal and in the headers, the "User-Agent" key held a value with the mismatching bundle id (e.g: "AlexisBarreyat.BeReal.135731" (or smth. like that) and because of this, I got a Bad request (400). I didn't manage to look into this any further for now. |
So, in short words the bundle ids don't match and that's why this happens. I didn't really understand which bundle id is supposed to be the one which matches but I looked into your ipa for sideload and the bundle id that it contains is "AlexisBarreyat.BeReal" is it supposed to be "com.yan.bea"? |
|
No, you are getting something wrong here. "The bundleIds resource represents the app's unique identifier that you can register, modify, and delete. " (https://developer.apple.com/documentation/appstoreconnectapi/bundle_ids). The original bundle id of the BeReal ipa is "AlexisBarreyat.BeReal". And the one you sideload should also have this exact bundle id. The bundle id of Bea as a tweak / deb is "com.yan.bea" but as I said, this doesnt matter in any way. Just make sure that the IPA you sideload has it's original bundle identifier set. |
|
Now I see, it's strange tho cause I made sure that the sideloaded ipa had that exact bundle id but it stills doesn't work. The same error. |
This error seems to mean that your phone number got blacklisted. Maybe this was the problem since the beginning? Just bereal detecting and blacklisting phones numbers which are using third party loggers? |
|
Well, you were correct. The bundle ids will not be the same if you use methods like alt/sidestore. They mangle bundle id (for some strange reason) I will try using other programs and see if bID match |
|
How are you getting to the conclusion that this error means your number got blacklisted? In fact, it doesn't. It's just that the headers contain a false User-Agent afaik. I signed up with the same phone number on the normal BeReal IPA after having gotten a "Bad request" trying to sign up with the sideloaded ipa. |
Yup as I told, I'm a dumb ass fuck |
|
@h4rqq Please keep me posted (via this thread) if you find a way how to get this to work :) |
|
@yandevelop It's not possible to sideload an app with a bundle identifier which is already registered at Apple. So, Bea can't have the same bundle identifier as BeReal. 🤔 |
|
Which is your method of sideloading BeReal? Do you just inject directly using app manager for example or just sideload it? |
|
I thought bundle identifiers were stored locally but I tried using the bundle id from an app which I have never installed and got the same error. Sideloading with the exact same bundle id seems not to be possible. Don't know how to proceed at this point |
Let's better not hope for something. If BeReal now uses its unique bundle identifier to accept or reject requests then people which don't have a jailbroken or a trollstore-compatible device are screwed 🤷♂️ |
|
I'm using TrollStore to sideload. The problem is definitely fixable. See https://www.reddit.com/r/AltStore/s/gSN6iCxbag |
|
So, IIUC, currently it is not possible to install the app using sideloadly or AltStore but only if your phone is jailbroken / you use troll store, but @yandevelop, you think you can get it back to work also with Sideloadly/AltStore? |
|
Yes. Just need time |
|
At least now we now a little bit about why this happens. If you are using trollstore to sideload, most likely bea's bundle id is exactly the same as the original and that's why you couldn't replicate the error. Well, I just hope we find a way to remove the string linked to our apple ids or a workaround ;) |
|
@yandevelop I hope your exams went well! Any chance you will fix this issue in the next couple of weeks? |
|
@yandevelop sup bro, how you are handling with your exams by far? I'm here to ask you if it is possible to find a way to make sideloaded bea "spoof" its own bundle id so that the requests made to log in don't get rejected by BeReal. Sorry for asking you for help idk if you already finished with your tests. |
|
@yandevelop https://github.com/yandevelop/Bea/releases/tag/1.3.7 won't fix the issue with Sideloadly/AltStore, or am I mistaken? |
|
You're perfectly right. If it was fixed it would be mentioned in changelog. |
|
@Ein-Tim please try this one: https://easyupload.io/8u2dtt. Couldn't test this myself for now unfortunately but that might fix the sideloading issues |
|
@yandevelop I just tried using AltStore and can confirm it is working! Thanks! |
Can confirm it working on iPhone 14 Pro 17.4.1, with the exception of a missing download button. All other Bea features do work. |
Keep getting this when I enter the otp. The code is definitely right.
The text was updated successfully, but these errors were encountered: