Can't sign into my ABS server on v2.0

[gh0sti]

I sideloaded the app with sidestore and the app crashes immediately after I try to sign in with my server URL and username and password. Now the app won't even launch without crashing.

ABS: v2.6.0 docker

[rasmuslos]

How are you logging in, using the local strategy or sso?

[gh0sti]

How are you logging in, using the local strategy or sso?

Local

[rasmuslos]

Try reinstalling the app, there has been a change in the underlying architecture to allow app extensions to function properly. Removing all data by uninstalling the app should fix the issue

[gh0sti]

Try reinstalling the app, there has been a change in the underlying architecture to allow app extensions to function properly. Removing all data by uninstalling the app should fix the issue

Did you upload a new build on github? Otherwise can I send you a private video of what happens when I log in and crash the app?

[rasmuslos]

You have to uninstall and then reinstall the app to delete all data. There was a change in the underlying database structure without a migration, so the app just crashes. I guess this is the reason why you are experiencing the crash. If this does not solve the issue please run the App using Xcode and provide the log output, otherwise cannot find out why the app behaves this way.

[gh0sti]

You have to uninstall and then reinstall the app to delete all data. There was a change in the underlying database structure without a migration, so the app just crashes. I guess this is the reason why you are experiencing the crash. If this does not solve the issue please run the App using Xcode and provide the log output, otherwise cannot find out why the app behaves this way.

Which I have done. What I'm doing is sideloading the app from SideStore https://sidestore.io/

This allows for sideloading apps on device going forward. Your app crashes right after I sign into my server.

[noneme]

hmm... same situation. When installed using SideStore or AltStore, the application crashes.
When signing and installing an application using SideLoadly, the application also crashes :-(
When installing the application using XCode (replacing the Bundle Identifer and App Group with your own), the application will generate an error when building
Thread 1: Fatal error: Unable to find App Group Container in Entitlements: group.io.rfk.shelfplayer)

[gh0sti]

hmm... same situation. When installed using SideStore or AltStore, the application crashes.

When signing and installing an application using SideLoadly, the application also crashes :-(

When installing the application using XCode (replacing the Bundle Identifer and App Group with your own), the application will generate an error when building

Thread 1: Fatal error: Unable to find App Group Container in Entitlements: group.io.rfk.shelfplayer)

I'm glad I'm not the only one.

[benonymity]

You have to change the group name in the app config in Xcode, then change the crashing line to reference the new group name and it builds fine.

[rasmuslos]

Yes, this is the solution. I put most things related to the database in an app group as data that is stored there is also available in app extensions. This is important for Siri integration, etc.

I have thought about a possible solution over the last few days, but the best thing I could think of is to just not use a shared group when side-loading. Right now the impact would be pretty small, as nothing makes use of the shared data just yet. Also in the future when there is a Siri integration it will not affect most people that are side-loading using AltStore, because you have to be a part of the Apple Developer program for Siri to work. Also, most people strip app extensions becuase they count towards the identifier limit of 10.

Anyone that is part of the Apple Developer programm propably has Xcode installed and can make the required changes themselves. It is sadly not possible to get the available app groups programmatically.

[noneme]

You have to change the group name in the app config in Xcode, then change the crashing line to reference the new group name and it builds fine.

yes, it works

[noneme]

Yes, this is the solution. I put most things related to the database in an app group as data that is stored there is also available in app extensions. This is important for Siri integration, etc.

I have thought about a possible solution over the last few days, but the best thing I could think of is to just not use a shared group when side-loading. Right now the impact would be pretty small, as nothing makes use of the shared data just yet. Also in the future when there is a Siri integration it will not affect most people that are side-loading using AltStore, because you have to be a part of the Apple Developer program for Siri to work. Also, most people strip app extensions becuase they count towards the identifier limit of 10.

Anyone that is part of the Apple Developer programm propably has Xcode installed and can make the required changes themselves. It is sadly not possible to get the available app groups programmatically.

okay! thank you!
What's up with the App Store? ;-)

[noneme]

Yes, this is the solution. I put most things related to the database in an app group as data that is stored there is also available in app extensions. This is important for Siri integration, etc.

I have thought about a possible solution over the last few days, but the best thing I could think of is to just not use a shared group when side-loading. Right now the impact would be pretty small, as nothing makes use of the shared data just yet. Also in the future when there is a Siri integration it will not affect most people that are side-loading using AltStore, because you have to be a part of the Apple Developer program for Siri to work. Also, most people strip app extensions becuase they count towards the identifier limit of 10.

Anyone that is part of the Apple Developer programm propably has Xcode installed and can make the required changes themselves. It is sadly not possible to get the available app groups programmatically.

problem Thread 1: Fatal error: Unable to find App Group Container in Entitlements: group.io.rfk.shelfplayer)
I decided like this:

https://stackoverflow.com/questions/42853052/how-to-get-app-groups-name-programmatically
https://stackoverflow.com/questions/25897086/obtain-bundle-identifier-programmatically-in-swift

[rasmuslos]

Yes, this is the solution. I put most things related to the database in an app group as data that is stored there is also available in app extensions. This is important for Siri integration, etc.
I have thought about a possible solution over the last few days, but the best thing I could think of is to just not use a shared group when side-loading. Right now the impact would be pretty small, as nothing makes use of the shared data just yet. Also in the future when there is a Siri integration it will not affect most people that are side-loading using AltStore, because you have to be a part of the Apple Developer program for Siri to work. Also, most people strip app extensions becuase they count towards the identifier limit of 10.
Anyone that is part of the Apple Developer programm propably has Xcode installed and can make the required changes themselves. It is sadly not possible to get the available app groups programmatically.

problem Thread 1: Fatal error: Unable to find App Group Container in Entitlements: group.io.rfk.shelfplayer) I decided like this:

https://stackoverflow.com/questions/42853052/how-to-get-app-groups-name-programmatically https://stackoverflow.com/questions/25897086/obtain-bundle-identifier-programmatically-in-swift

I am not quite sure if this will work because I don't know how AltStore changes group identifiers, but I don't think this will work.
Can you send a Screenshot of the "App Groups" section on the "Signing & Capabilities" page in Xcode? All your group identifiers, include the ones made by AltStore should be listed there.

[rasmuslos]

Yes, this is the solution. I put most things related to the database in an app group as data that is stored there is also available in app extensions. This is important for Siri integration, etc.
I have thought about a possible solution over the last few days, but the best thing I could think of is to just not use a shared group when side-loading. Right now the impact would be pretty small, as nothing makes use of the shared data just yet. Also in the future when there is a Siri integration it will not affect most people that are side-loading using AltStore, because you have to be a part of the Apple Developer program for Siri to work. Also, most people strip app extensions becuase they count towards the identifier limit of 10.
Anyone that is part of the Apple Developer programm propably has Xcode installed and can make the required changes themselves. It is sadly not possible to get the available app groups programmatically.

okay! thank you! What's up with the App Store? ;-)

I would like to know, too...

[noneme]

Yes, this is the solution. I put most things related to the database in an app group as data that is stored there is also available in app extensions. This is important for Siri integration, etc.
I have thought about a possible solution over the last few days, but the best thing I could think of is to just not use a shared group when side-loading. Right now the impact would be pretty small, as nothing makes use of the shared data just yet. Also in the future when there is a Siri integration it will not affect most people that are side-loading using AltStore, because you have to be a part of the Apple Developer program for Siri to work. Also, most people strip app extensions becuase they count towards the identifier limit of 10.
Anyone that is part of the Apple Developer programm propably has Xcode installed and can make the required changes themselves. It is sadly not possible to get the available app groups programmatically.

problem Thread 1: Fatal error: Unable to find App Group Container in Entitlements: group.io.rfk.shelfplayer) I decided like this:
https://stackoverflow.com/questions/42853052/how-to-get-app-groups-name-programmatically https://stackoverflow.com/questions/25897086/obtain-bundle-identifier-programmatically-in-swift

I am not quite sure if this will work because I don't know how AltStore changes group identifiers, but I don't think this will work. Can you send a Screenshot of the "App Groups" section on the "Signing & Capabilities" page in Xcode? All your group identifiers, include the ones made by AltStore should be listed there.

Certainly:

installed using Xcode, works

[rasmuslos]

Yes, this is the solution. I put most things related to the database in an app group as data that is stored there is also available in app extensions. This is important for Siri integration, etc.
I have thought about a possible solution over the last few days, but the best thing I could think of is to just not use a shared group when side-loading. Right now the impact would be pretty small, as nothing makes use of the shared data just yet. Also in the future when there is a Siri integration it will not affect most people that are side-loading using AltStore, because you have to be a part of the Apple Developer program for Siri to work. Also, most people strip app extensions becuase they count towards the identifier limit of 10.
Anyone that is part of the Apple Developer programm propably has Xcode installed and can make the required changes themselves. It is sadly not possible to get the available app groups programmatically.

problem Thread 1: Fatal error: Unable to find App Group Container in Entitlements: group.io.rfk.shelfplayer) I decided like this:
https://stackoverflow.com/questions/42853052/how-to-get-app-groups-name-programmatically https://stackoverflow.com/questions/25897086/obtain-bundle-identifier-programmatically-in-swift

I am not quite sure if this will work because I don't know how AltStore changes group identifiers, but I don't think this will work. Can you send a Screenshot of the "App Groups" section on the "Signing & Capabilities" page in Xcode? All your group identifiers, include the ones made by AltStore should be listed there.

Certainly:

installed using Xcode, works

Just below that :)

[noneme]

Just below that :)

[rasmuslos]

Just below that :)

So it looks like AltStore appends some id (I don't think it's your developer id) to the group id. I will have a look at the AltStore repo to find out if using the bundle identifier is a viable solution, but it might take some time.

[noneme]

So it looks like AltStore appends some id (I don't think it's your developer id) to the group id. I will have a look at the AltStore repo to find out if using the bundle identifier is a viable solution, but it might take some time

ok, but for me it’s not urgent! this is more for research purposes ;-)

[rasmuslos]

@noneme @gh0sti can you test this build? It should use the correct group identifier: https://github.com/rasmuslos/ShelfPlayer/releases/tag/v2.0.2

[gh0sti]

@noneme @gh0sti can you test this build? It should use the correct group identifier: https://github.com/rasmuslos/ShelfPlayer/releases/tag/v2.0.2

it worked! thanks I was able to sign in

[gh0sti]

This is resolved.

[rasmuslos]

Great 👍