Can’t login

[sergue22]

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

[Ein-Tim]

@h4rqq Did you ensure that the bundle ID wasn't changed? I also tried using sideloadly and as reported above it actually changed the bundle ID.

[h4rqq]

I say this because I was able to use Bea without any problems a couple months ago but now that error Is always present

[h4rqq]

@h4rqq Did you ensure that the bundle ID wasn't changed? I also tried using sideloadly and as reported above it actually changed the bundle ID.

Well, some sideloaders like SideStore, altstore and sideloadly ,indeed change bundle ids

Edit: they are supposed to change apps ids not bundle

[h4rqq]

So, I did some research and found out that sideloaders only change app ids not bundle (supposedly) but there's a bunch of things weird with sideloading and this could be possible in some cases, other thing that I found out is that bundle ids are stored locally so maybe there was one or more things that got corrupted/changed in the process and could be fixed with a pc, and finally my own theory about all this is that BeReal detects if the app is sideloaded or not, this can be done by looking at the app id, and rejects every request made on that sideloaded BeReal. I will try changing the bundle id to another one and deleted original BeReal, if this doesn't work I will look for BeReal's bID locally and see if it was stored or deleted, maybe iOS stores bID?

[h4rqq]

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

[yandevelop]

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.

[h4rqq]

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"?

[yandevelop]

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.

[h4rqq]

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.

[h4rqq]

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.

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?

[h4rqq]

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

[yandevelop]

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.

[h4rqq]

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

[Ein-Tim]

@h4rqq Please keep me posted (via this thread) if you find a way how to get this to work :)

[h4rqq]

@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. 🤔

[h4rqq]

Which is your method of sideloading BeReal? Do you just inject directly using app manager for example or just sideload it?

[h4rqq]

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

[h4rqq]

@h4rqq Please keep me posted (via this thread) if you find a way how to get this to work :)

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 🤷‍♂️

[yandevelop]

I'm using TrollStore to sideload. The problem is definitely fixable. See https://www.reddit.com/r/AltStore/s/gSN6iCxbag

[Ein-Tim]

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?

[yandevelop]

Yes. Just need time

[h4rqq]

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 ;)

[BZHugs]

CF: https://github.com/rvaidun/befake/issues/199

[Ein-Tim]

@yandevelop I hope your exams went well! Any chance you will fix this issue in the next couple of weeks?

[h4rqq]

@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.

[Ein-Tim]

@yandevelop https://github.com/yandevelop/Bea/releases/tag/1.3.7 won't fix the issue with Sideloadly/AltStore, or am I mistaken?

[yandevelop]

You're perfectly right. If it was fixed it would be mentioned in changelog.

[yandevelop]

@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

[Ein-Tim]

@yandevelop I just tried using AltStore and can confirm it is working! Thanks!

[TwentyFour-24]

@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

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.