Skip to content

Add Bluetooth background modes to Intents extensions#1033

Open
globalhuman wants to merge 1 commit into
holzschu:masterfrom
globalhuman:add-bluetooth-background-modes
Open

Add Bluetooth background modes to Intents extensions#1033
globalhuman wants to merge 1 commit into
holzschu:masterfrom
globalhuman:add-bluetooth-background-modes

Conversation

@globalhuman

Copy link
Copy Markdown

This adds Bluetooth background mode declarations to the a-Shell and a-Shell mini Intents extensions so Bluetooth central and peripheral use can be enabled from the extension context.

The change is limited to the extension Info.plist files.

@holzschu

Copy link
Copy Markdown
Owner

The upload failed:

Invalid Info.plist value. The Info.plist key UIBackgroundModes in the “a-Shell-mini.app/PlugIns/a-Shell-mini-Intents.appex” bundle contains an invalid value: “bluetooth-peripheral”. For more information, refer to the Information Property List Key Reference.
The server’s response was: ‘{
    code = 91092;
    description = "Invalid Info.plist value. The Info.plist key UIBackgroundModes in the \U201ca-Shell-mini.app/PlugIns/a-Shell-mini-Intents.appex\U201d bundle contains an invalid value: \U201cbluetooth-peripheral\U201d. For more information, refer to the Information Property List Key Reference.";
}’.

Invalid Info.plist value. The Info.plist key UIBackgroundModes in the “a-Shell-mini.app/PlugIns/a-Shell-mini-Intents.appex” bundle contains an invalid value: “bluetooth-central”. For more information, refer to the Information Property List Key Reference.
The server’s response was: ‘{
    code = 91092;
    description = "Invalid Info.plist value. The Info.plist key UIBackgroundModes in the \U201ca-Shell-mini.app/PlugIns/a-Shell-mini-Intents.appex\U201d bundle contains an invalid value: \U201cbluetooth-central\U201d. For more information, refer to the Information Property List Key Reference.";
}’.

@globalhuman globalhuman force-pushed the add-bluetooth-background-modes branch from a9d93cb to cee5dca Compare June 13, 2026 00:41
@globalhuman

Copy link
Copy Markdown
Author

I am investigating. I notice that this repo doesn't have many updates which doesn't line up with the numerous a-shell updates in the AppStore and TestFlight.

Are there changes that need to be pushed here so that I can continue working on this?

Is there a specific branch I should base my work off?

@holzschu

Copy link
Copy Markdown
Owner

As I said in your other PR, the currently active branch is SwiftTerm2, but it will soon be merged. That's not a big issue because your changes are small enough that I can merge them manually.

@globalhuman

Copy link
Copy Markdown
Author

The branch as available to the public on this repo is 3 months stale. In case you run a git mirror elsewhere and need to push it that would be appreciated. This branch and main do not have any of the changes that I've seen in the release notes of recent times.

https://github.com/holzschu/a-shell/tree/SwiftTerm2

@holzschu

Copy link
Copy Markdown
Owner

Thanks for the explanation; indeed I forgot to push my changes for the past 3 months. That should look more active now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants