Apple IOS app request

[autumn vapor]

Email (for TestFlight): [e-mail]
Use Case:

• Want to use iOS device as a node for camera/location/notification capabilities
• Planning to integrate with my OpenClaw Gateway for device pairing and remote control
• Interested in voice and canvas features on mobile
  Current Setup:
• Running OpenClaw Gateway on windows WSL
• Using feishu as primary channel
• Active user, running multiple cron jobs, sub-agents, and dashboard
  Device:
• iPhone 16 pro max
• IOS 26.3

[rocky fulcrum]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[hot dawn]

Thanks — this is exactly the kind of “mobile node” use case we want (camera / location / notifications paired to your Gateway).

A couple quick checks so we don’t waste your time on the first build:

1. TestFlight email
   Make sure the email you posted is the one tied to your Apple ID (the address you use for TestFlight). If it’s different, post the correct one (or just the domain + last 3 chars, and say “I’ll share full email when asked” if you prefer).

2. iOS version
   You’re on iOS 26.3 (sounds like a beta). Totally fine to try, but beta iOS can break background location/notifications unexpectedly — if anything is flaky, that’s the first suspect.

3. Networking / pairing expectation
   Do you expect the phone to pair + be reachable only on the same LAN, or also remotely (cellular / different network)? That affects the “it just works” experience a lot.

4. Priority order
   If you had to pick the first thing to validate on day 1, is it:

• A) location pings
• B) camera snapshots

• C) push notifications to the phone
• D) voice/canvas experiments on mobile

Reply with (3) + (4) and we’ll know what to optimize the first TestFlight round for.

[autumn vapor]

Thank you for your reply.
1）My Apple ID is: [e-mail].
2）iOS 26.3 is the latest official public release version (not a beta).
3）I would like the phone to be accessible remotely (over cellular or different networks). I have a domain that can access my own server.
4）I choose D) voice/canvas experiments on mobile as the first priority to validate.
Looking forward to receiving the invitation.

[hot dawn]

Perfect — got it.

• TestFlight email: noted as [e-mail] (Apple ID email). Once you’re added, Apple will send a TestFlight invite email—check spam/promotions if it doesn’t show up.
• iOS version: thanks for clarifying. (Quick sanity check: Apple’s “official public” iOS versions usually show as e.g. 18.x/17.x — if you have a second, can you paste the exact string from Settings → General → About → iOS Version? Just so we target the right OS behaviors for mic/background tasks.)
• Remote access (cellular/different networks): your domain helps as long as your Gateway is reachable from the public internet over HTTPS/WebSocket. On iOS, “remote node control” usually needs the phone to maintain an outbound connection and/or be wakeable via push; inbound connections directly to the phone over cellular are generally not realistic.
• Priority D (voice/canvas): awesome. For first validation, are you aiming for:

1. voice input (mic streaming / dictation),
2. voice output (TTS playback), and/or
3. canvas viewing + interaction (buttons/forms/etc.)?

Answer with 1/2/3 and the exact iOS version string, and that should be enough to line you up for the right TestFlight build/testing checklist.

[autumn vapor]

1）In Settings → General → About, the iOS version shows as 26.3. When I tap on the version number, it further displays iOS 26.3 (23D127).
2）Regarding “Priority D (voice/canvas)”, I would like to prioritize canvas viewing + interaction (buttons/forms/etc.) at this stage.
3）Also, may I ask approximately how long it will take for the TestFlight invitation to be sent?

[hot dawn]

Nice, thanks — iOS 26.3 (23D127) is a super helpful level of detail to have on record.

For priority = canvas viewing + interaction, a couple specifics that would help us validate the right things early:

• Do you mostly want “live canvas” updates while an agent is running (streaming/refreshing), or is static render + tap interactions enough for now?
• What interaction types matter most at this stage: buttons, text inputs/forms, file upload, scrollable layouts, web links, etc.?

On TestFlight invite timing: I can’t personally send it from here, and it depends on when the next batch of testers is added, but typically it’s within 1–3 days once someone is doing invites. If you don’t see anything after ~5 days, reply again in this thread and we’ll re-check that you didn’t get missed. Also: make sure the TestFlight app is installed, and keep an eye on spam/promotions.

[autumn vapor]

1）For now, static rendering + tap interactions are sufficient. The interaction types I care most about at this stage are buttons and file input/forms.
2）I already have the TestFlight app installed and I’m looking forward to your invitation.

[hot dawn]

Got it — static canvas + tap interactions, with buttons + file input/forms as the key interaction types. That’s a great “MVP surface” to validate first.

For the file input bit on iOS, one quick detail that affects the UX a lot: do you mainly want files from iCloud Drive / Files app, or also Photos/Camera (pick an image / take a photo) as an input source?

Re: TestFlight — cool that you already have it installed. Invite timing is still usually 1–3 days once invites go out; if you don’t see it after ~5 days, reply here and we’ll re-check that your Apple ID email didn’t get skipped.

[autumn vapor]

Files app or Photos/Camera

[hot dawn]

Perfect — noted: you want both as input sources (Files app/iCloud Drive and Photos/Camera).

One follow-up so we implement the right picker behavior on iOS: for Photos, do you need multi-select (upload several images at once), or is single file/image enough for the first iteration?

[autumn vapor]

I’ll be able to answer that after I’ve had a chance to try it out.

[hot dawn]

Totally fair — let’s treat multi-select as a “nice to have” until you’ve tried the first build.

For the first iteration we’ll usually default to single file/image (it’s simpler + more reliable on iOS), and then you can tell us whether multi-select is actually necessary after testing.

When you do get to try it, the most useful feedback is:

• did Files picking work (iCloud/local)
• did Photos picking work
• did Take Photo → attach work
• and whether you immediately wished you could attach 2+ items at once (and what the real use case was)

Just drop that back in this thread when you’ve had hands-on time.

[autumn vapor]

No problem 👍

[hot dawn]

Cool — thanks. We’ll assume single-item attach for the first pass, and you can tell us after a quick real-world try whether multi-select is actually needed.

When you get the TestFlight build, just reply here with how Files / Photos / Take Photo → attach feel on iOS 26.3, and we’ll iterate from there. If the invite doesn’t show up after ~5 days, reply in this thread and we’ll re-check the list.

[autumn vapor]

My iOS app test invitation hasn’t come through yet. When was this invitation sent? I’m eagerly looking forward to it.

[autumn vapor]

It has been five days, and I still haven’t received the test invitation. Could you please help check the status? Thank you very much.

[autumn vapor]

It has been five days, and I still haven’t received the test invitation. Could you please help check the status? Thank you very much

[hot dawn]

I can’t directly see the TestFlight invite list from here, but I’ve flagged this internally so we can re-check and re-send if needed.

In the meantime, a couple quick things to rule out (these are the common gotchas with TestFlight invites):

• Make sure TestFlight is installed on the iPhone, and you’re signed into the same Apple ID you want to test with.
• Check your email’s Spam/Junk/Promotions folders for an Apple/TestFlight invite.
• Confirm the email you want invited is still: [e-mail] (and that this is the email tied to your Apple ID, or at least reachable for the invite link).
• If you have a second Apple ID on the device, the invite can look “missing” even if it arrived—switching Apple IDs in TestFlight can matter.

If you reply with “yes, that email is correct” (or paste an alternate email you prefer), we’ll try another send and you should usually see it within ~24 hours.

[autumn vapor]

yes, that email is correct

[hot dawn]

Got it — confirmed: [e-mail].

I’ve forwarded this for a re-send of the TestFlight invite. If everything’s behaving, you should see it land within ~24 hours.

If it still doesn’t show up after that, can you reply with:

1. the Apple ID email you’re signed into on the iPhone (Settings → your name), and
2. a screenshot of TestFlight → Settings (just the top part that shows which Apple ID TestFlight is using)

That usually makes it obvious whether it’s an invite-delivery issue vs. an Apple-ID mismatch.

[autumn vapor]

Is the invitation sent as an email with an invite link/code, or is it delivered directly within the TestFlight app?

[hot dawn]

Usually it’s an email invite that contains a “View in TestFlight” link (sometimes it’s also shareable as a public invite link, depending on how the beta is set up).

How it behaves on-device:

• Before you accept the invite: the app typically won’t just appear inside TestFlight on its own.
• After you tap the link (or open the public invite link) on the iPhone: it opens TestFlight, you accept, and then the app shows up under TestFlight → Apps.
• Some setups can also use a redeem code, but email/link is the most common.

So if you haven’t received anything yet, the key missing piece is usually the email/link (or a public invite link). If we can’t get email delivery to cooperate, we can switch to a public link approach for the beta.

[autumn vapor]

It’s been about 22 hours now and I still haven’t received the TestFlight invite.
I’ve checked my inbox and spam folder, but nothing has come through yet.
Could you please help check the status or resend it again? Thank you!

[hot dawn]

If there’s still nothing after ~22h (incl. spam), that usually means the invite didn’t actually go out (or it went to a different Apple ID/email than expected).

I can’t directly inspect the TestFlight console from Discord, but I can help us narrow it down fast—can you reply with:

1. The Apple ID email you’re currently signed into on the iPhone (Settings → your name), and
2. A screenshot of TestFlight → Settings (top area showing the Apple ID), and
3. Confirm your invite email is exactly [e-mail] (no “+alias”, no typo).

Also: if you have an iCloud email for that Apple ID, it’s worth trying that as the invite address—Gmail sometimes just “disappears” in delivery pipelines.

Once you post (1) + (2), we can decide whether to re-send or switch to a public TestFlight invite link (if enabled), which avoids email delivery issues entirely.

[autumn vapor]

I confirm the email is correct.
How should I provide (1) and (2)?
What’s the best way to send you that info?

[hot dawn]

Just post them here in this thread (Discord), that’s the easiest.

(1) Apple ID email:

• On iPhone: Settings → your name (Apple Account) → Sign-In & Security
• Copy/paste the email shown there and send it as plain text.

(2) TestFlight screenshot:

• Open TestFlight → Settings
• Take a screenshot of the top section where it shows which Apple ID TestFlight is using
• Upload it directly to Discord (drag/drop or “+” → Photo).

Privacy note: it’s fine if the screenshot shows your email, but please blur/cover anything sensitive like your full name, phone number, or other personal details if they appear.

If you’d rather not post the email publicly, you can instead:

• share only the domain + a redacted version (e.g. b***[e-mail]), and
• we’ll switch to a public TestFlight invite link approach (if enabled) so we don’t need the exact email for delivery.

[autumn vapor]

1）The primary email under Sign-In & Security is [e-mail]. I also checked my iCloud mailbox, but there is no invite there either.
2）I confirmed that TestFlight is logged in with the same Apple ID, but I’m unable to provide a screenshot at this time.

[hot dawn]

Perfect — that rules out the most common mismatch (different Apple ID in Settings vs TestFlight).

At this point, if you’re not getting any TestFlight email after multiple days, it’s usually one of these on the App Store Connect side:

• your address isn’t actually in the tester list / correct tester group, or
• the build isn’t assigned to the external testing group, or
• Apple’s invite email just isn’t delivering (rarer, but it happens).

Two fastest paths forward:

1. Try a different invite address (recommended)

• If you have any alternate email you can receive on the phone (iCloud email or another Gmail), paste it here and we’ll add that one too. This often bypasses weird delivery issues.

2. Switch to a public TestFlight invite link (if enabled)

• This avoids email delivery entirely: you open the link on the iPhone → it jumps into TestFlight.
• If you’re OK with that approach, reply “public link ok” and we’ll use that route.

Optional quick check on your side (sometimes the invite is there but buried):

• In Gmail, search: TestFlight and also from:[e-mail] and App Store Connect.

Reply with either an alternate email to try, or “public link ok”, and we’ll proceed with the quickest one.

[autumn vapor]

public link ok

[hot dawn]

Awesome — public link is the cleanest workaround when TestFlight email delivery is flaky.

Next step on our side: we’ll enable/generate a public TestFlight invite link for the beta (it’s an App Store Connect setting) and then post the link in this thread. Once you open it on your iPhone, it should jump straight into TestFlight and let you accept.

On your side (quick prep):

• Make sure TestFlight is installed
• Open the link on the iPhone (Safari is best)

As soon as the link is ready I’ll drop it here. If you don’t see it within ~24h, reply again and we’ll re-check that the build is actually assigned to the public link group.

[autumn vapor]

TestFlight is already installed and I’m waiting for your link.

[hot dawn]

Nice — then you’re ready on your side.

Just to be transparent: I can’t generate the public TestFlight link myself from Discord (it has to be created in App Store Connect by someone with access to the iOS app listing + TestFlight groups). Once that link is generated, it’ll look like:

https://testflight.apple.com/join/<CODE>

…and we’ll post it right here in this thread.

As soon as you see it:

• open it on the iPhone (Safari is best)
• it should jump into TestFlight → Accept → Install

If you don’t see the link posted within the next day, reply again and we’ll treat it as “link not enabled / build not assigned to the public group yet” and get the TestFlight setup corrected.

[autumn vapor]

No problem. I’m familiar with redeeming TestFlight access via the link method.
I’ll wait for the link.

[hot dawn]

Sounds good.

Once the public invite link is generated on the App Store Connect side, we’ll post the testflight.apple.com/join/... link in this thread. If you don’t see it show up by tomorrow (UTC), reply again here and we’ll treat it as “public link not enabled / build not assigned” and get that corrected.

[autumn vapor]

Hi, just checking on the status of my access.

[hot dawn]

Still no update I can see from my side — and I also don’t have App Store Connect access, so I can’t directly verify whether the public invite link has been generated / enabled yet.

What I can say: if the link isn’t posted here yet, it likely means one of these is still pending on the App Store Connect side:

• public link not enabled for the TestFlight group, or
• the build hasn’t been assigned to that group, or
• external testing / beta review step is blocking it (sometimes Apple gates things)

I’ve re-surfaced this again so someone with App Store Connect access can either:

• post the https://testflight.apple.com/join/... link here, or
• confirm what’s blocking it.

If you want a faster fallback while we wait: share a second email you can receive on the phone (iCloud or another Gmail) and we’ll try adding that too (sometimes delivery to one address is just cursed).

[autumn vapor]

Alright, I’ll continue to wait.
Alternatively, you can also try sending the invite to [e-mail] and see if that works better.

[hot dawn]

Got it — thanks. I’ll have the TestFlight admin side add [e-mail] as an additional tester email and try sending the invite there as well.

A couple notes so you know what to expect:

• If the iCloud invite works, you should get the usual “View in TestFlight” email/link (and then it appears inside TestFlight after you accept).
• In parallel, we’re still aiming for the public TestFlight link route, since that bypasses email delivery completely once it’s enabled/assigned.

If you don’t see anything to [e-mail] within ~24h either, the likely cause is no longer email delivery — it’s usually that the build/group/public-link setup in App Store Connect isn’t fully enabled/assigned yet. In that case we’ll push for the public link to be posted here.

[autumn vapor]

What is the name of the app that I’ll be testing?

[hot dawn]

I don’t know the exact TestFlight display name yet (I don’t have App Store Connect access, so I can’t see what it’s currently published as), so I don’t want to guess and accidentally tell you the wrong name.

Good news: when you open the invite (email or public link), TestFlight will show the app name + the developer before you install. When we post the public link here, I’ll also include “you should see it as: <app name>” once I have that confirmed from the person generating the link.

[autumn vapor]

I still haven’t received the invitation yet. Could you please check if it was sent successfully, or resend it to me?

[hot dawn]

I still can’t directly check “was the invite sent?” or resend it myself (that has to happen in App Store Connect), and my internal memory lookup tool is currently erroring, so I can’t even confirm whether someone already tried the iCloud add on their side.

Given you’ve received nothing to both [e-mail] and [e-mail], this is almost certainly not an email-spam issue anymore — it’s usually one of these App Store Connect setup blockers:

• your emails aren’t actually added to the correct TestFlight tester group, and/or
• there isn’t a build assigned to that group, and/or
• External Testing isn’t enabled / is waiting on Beta App Review, and/or
• the public invite link hasn’t been enabled for that group (or enabled but no build assigned)

Best next step (fastest): we need someone with App Store Connect access to enable the public link and paste the https://testflight.apple.com/join/... URL here.

While we wait, if you’re willing: paste one more alternate email (any address you can receive immediately on the phone). If email delivery is “cursed” for the first two, a third address sometimes succeeds—but the public link is still the cleanest fix.

[autumn vapor]

I’d prefer to proceed with the public invite link instead. Could you please let me know when I can expect to receive the link?