You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Previous developer accounts soft-locked by SideStore again #1156
This issue has come back. It was previously mentioned in issue #410 , and supposed to be fixed in pull #508, but has come back again for a while now.
Enrolling in the Developer Program removes the sideloading limits for an account even after your membership has expired. Because of this App IDs do not actually expire so for example I currently have 62 App IDs on my account, some from multiple years ago. The issue is that SideStore sees that I'm a "Free Developer Account" and assumes that I have the 10 App ID limit and shows "0 App IDs Remaining" and seems to make that check before any install so that I am unable to install any applications beside SideStore itself. If I install applications manually using AltServer (not SideServer since it revokes my certificate every time) then I'm able to have an infinite amount of applications installed at the same time with the 365 day expiry.
Instructions to reproduce
Become a member of Apple's Developer Program.
Let your membership lapse.
Use more App IDs than what is available with a free acount.
You're now locked from using SideStore.
What version of SideStore are you using?
0.6.2
Other info
This issue has come back. It was previously mentioned in issue #410 , and supposed to be fixed in pull #508, but has come back again for a while now.
As I can see this issue is still open, I’d like to chip in my two cents and advise I’m also experiencing the exact same issue. I’m running Version 0.6.4-20260620.1099+682a7972.
Currently, my workaround is to sideload apps using iLoader to get the app ID registered before proceeding to continue on with SideStore for future updates and reinstalls as my app IDs on my legacy dev account do not expire.
I hope we can get this fixed promptly as the issue does make installing new apps rather cumbersome.
Hi LimaHotel, @LimaHotel807
The good thing is that if you know this is the issue you face, you can fork it and build it yourself and fix the issue for yourself temporarily. The patch is just removing a few lines. See my earlier pull request.
Activity
duronald commentedon Feb 20, 2026
Can someone walk me through the Github Actions build process? I believe I've identified the issue but don't have a Mac to build Sidestore. It seems like commit 3682b65 relative to 731d270#diff-d72de7a18a53e4a153f99f87a3c84513303aca9d574325e7b7aa216bcfa4800a reintroduced the issue with
duronald commentedon Feb 20, 2026
Or can someone generate a test build so I can try?
duronald commentedon Feb 20, 2026
#1177
I built it and tested it and can confirm that the suspected regression was the cause.
LimaHotel807 commentedon Jun 21, 2026
Hi all,
As I can see this issue is still open, I’d like to chip in my two cents and advise I’m also experiencing the exact same issue. I’m running Version 0.6.4-20260620.1099+682a7972.
Currently, my workaround is to sideload apps using iLoader to get the app ID registered before proceeding to continue on with SideStore for future updates and reinstalls as my app IDs on my legacy dev account do not expire.
I hope we can get this fixed promptly as the issue does make installing new apps rather cumbersome.
duronald commentedon Jun 21, 2026
Hi LimaHotel,
@LimaHotel807
The good thing is that if you know this is the issue you face, you can fork it and build it yourself and fix the issue for yourself temporarily. The patch is just removing a few lines. See my earlier pull request.
LimaHotel807 commentedon Jun 21, 2026
Hi @duronald
Unfortunately, I don't own a Mac so I'm not able to build a working version for myself.
duronald commentedon Jun 21, 2026
I don’t own one either. You can build the whole thing using GitHub Actions when you fork the repo.
LimaHotel807 commentedon Jun 21, 2026
Oh really? That's quite interesting, I'll give that a try and see how it goes.
mahee96 commentedon Jul 16, 2026
I am closing this issue, since there have been many bug fixes recently.
if this issue still exists in latest NIGHTLY, create a new issue and link this as existing issue.
that way we can better track this, since the current version in the issue is 0.6.2 and is already too outdated.