thatmarcel / beepserv-rewrite

A small service that generates iMessage registration data on a jailbroken iPhone, now with an app and local state notifications
GNU Affero General Public License v3.0
57 stars 5 forks source link

identityservicesd crashes every 15-45 min #21

Open TheFloyds4240 opened 5 months ago

TheFloyds4240 commented 5 months ago
Dometalican commented 5 months ago

Hey boss. I'm experiencing the same issue but I find it peculiar that you're rootless while having the problem since I'm rootfull. I figure I'd ask:

  1. Do you have Ellekit installed on Sileo? It's not available for rootfull but if you don't have it, try installing it and rebooting the springboard.

  2. Have you tried the following:

a. Uninstall beepserv and sign out of Beeper Mini/uninstall it b. Pop the active SIM onto your iPhone and activate iMessage with Airplane Mode turned off. c. Once it's all active, put it back in Airplane mode and then toggle iMessage off d. Reinstall Beepserv and restart the Springboard (during this time, pull out the active SIM and reinsert it onto your Android device) e. Reinstall the latest Beeper Mini app from here: https://www.beeper.com/download f. Put in the new Registration Code and the phone number should activate without asking you to sign in.

See if this works for you.

TheFloyds4240 commented 5 months ago

I did try those steps and none worked. What's quite curious is that doing a factory reset on the iPhone, installing Palera1n Beta 9.1 (rootless), and not using Dopamine/meowbrek2 fixed the issue. In order to combat the almost daily crashes people have been reporting on Palera1n, I set up an automation for a daily userspace reboot.

Maybe you could give that a shot and see if we have similar results?

Dometalican commented 5 months ago

Well...I'm rootful (iPhone 6...no choice) so I only have Chimera and Checkra1n (last two times I tried Checkra1n, it crashed my iPhone). I'm at a loss.

I already reinstalled beepserv and rebooted springboard but it still cuts off after a bit. I pretty much have to wait until Marcel finds out why the tweak doesn't want to continue using cached validation.

thatmarcel commented 5 months ago

Thanks for the report! The reason why we can't keep using the cached validation data is that it expires after 10-15 minutes and it seems like generating new validation data every time might be a bit more reliable (not sure about that though).

To narrow down the cause of this issue, if you haven't already, maybe try release e0477ea and see if the crashes still happen.