Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(ios): name the app group and keychain the glance widget reads in the submission steps

nirholasbae5b23a43e0
diff --git a/ios/docs/SUBMISSION.md b/ios/docs/SUBMISSION.md
index e9935daa4..377208363 100644
--- a/ios/docs/SUBMISSION.md
+++ b/ios/docs/SUBMISSION.md
@@ -86,7 +86,13 @@ In Xcode:
1. Select the **App** target, Signing & Capabilities, choose the team. Confirm
Associated Domains lists `applinks:three.ws` and Push Notifications is
- present; both come from `App/App.entitlements`.
+ present; both come from `App/App.entitlements`. App Groups should list
+ `group.ws.three.app` and Keychain Sharing `ws.three.shared`, which are what
+ the Agent glance widget reads.
+1b. Select the **GlanceWidgetExtension** target and choose the same team. It
+ needs the same App Group and Keychain Sharing entries; both expand from
+ `DEVELOPMENT_TEAM`, so nothing else has to be typed. A build with no team on
+ this target fails to sign the .appex and the archive is rejected.
2. Set the marketing version and build number. `MARKETING_VERSION` is `1.0`
and `CURRENT_PROJECT_VERSION` is `1` in the project file; the build number
must increase on every upload.