Automated Apple Developer Device Audit
Every Monday, WebRun opens your Apple Developer account, counts the registered devices against the slots available for the membership year, lists provisioning profiles that still reference retired hardware, records the whole picture in Airtable, and files a dated copy of the device list in Google Drive.
How do I track Apple Developer device slots and stale provisioning profiles?
Every Monday WebRun opens your Apple Developer account, counts registered devices against the slots left in the membership year, and checks which provisioning profiles still reference retired hardware. It records the totals in Airtable and files a dated device list in Google Drive, so a test build never fails to install during launch week.
- Remaining device slots are known every week, not at the limit
- Profiles pointing at retired hardware are flagged for review
- A dated device list is filed for every week of the membership year
Built for iOS developers · release engineers · mobile teams · QA leads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
developer.apple.com/accountin a real browser with your saved login - no setup, no API keys. -
1
Apple Developer - count devices and slots
developer.apple.com
WebRun opens Apple Developer to count devices and slots. - Open your Apple Developer account and go to the registered devices list
- Count devices by platform and note how many slots remain for the membership year
- Capture the name, identifier, and date added for each device
- Open the provisioning profiles and note which devices each one includes
- Flag profiles that still include devices nobody has used in months
- Register and remove nothing. WebRun reads the account and leaves every change to you
Done when The device count, remaining slots, and every stale profile reference are captured.
-
2
Airtable - track slots and stale profiles
airtable.com
WebRun opens Airtable to track slots and stale profiles. - Keep one row per registered device with its identifier, platform, and date added
- Record the weekly totals: devices registered, slots left, profiles affected
- Flag the week the remaining slots drop below the threshold you set
- Mark devices that appear in no current provisioning profile as review candidates
Done when Airtable shows this week's slot count and the devices worth reviewing.
-
3
Google Drive - file a dated device list
drive.google.com
WebRun opens Google Drive to file a dated device list. - Save a dated copy of the full device list to your engineering folder
- Include the provisioning profiles and the devices each one references
- Keep previous weeks rather than overwriting, so you can see when a device was added
- Name the file with the date so the newest sorts to the top
Done when A dated device list for this week is filed in Drive alongside earlier ones.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it remove devices or regenerate profiles?
No. WebRun reads the device list and the provisioning profiles and reports what it finds. Removing a device, editing a profile, or resetting the list at renewal stays a deliberate action by your release engineer.
How does it decide a profile is stale?
It flags profiles that still include devices which appear nowhere in your current test fleet, and devices that belong to no current profile at all. Both are listed as review candidates, never removed.
When does it warn me about running out of slots?
Whenever the remaining slots for the membership year drop below the threshold you set. The Airtable record keeps the weekly trend, so you see it coming rather than hitting the limit in launch week.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.