It’s been a busy month working on APT and there’s more exciting things coming. If you’re interested in trying out the latest beta, you can download it here:
Version 3.5 brings a number of improvements and bug fixes to the multi-team capability as well as an all-new iOS app bundling feature! This feature is primarily for the times when the Xojo IDE can’t or won’t sign or build the app bundle for upload to the App Store but doesn’t give you enough information why. The IDE must still be able to build your app however.
The way this works is, if the Xojo IDE gives you an error when building for the App Store:
Select the Team for the account that you will be releasing the app from using the Teams menu.
From the Package menu, select Build.
APT will ask you for two things:
The .app bundle for your app
The entitlements plist file (clicking cancel will continue building without entitlements)
Once this information is gathered, APT will attempt to sign and bundle your app. If any errors occur, you will receive a message showing as much information as APT could gather to help you figure out what went wrong.
NOTE: If you have a build earlier than 3.5b11, you may have to manually download this version as we fixed a bug in the updater recently which prevented the update window from appearing.
So far so good on my end with 3.5. Also a great development on the new Package functionality. Personally I’ve never run into a problem with Xojo signing my apps, but this could be worth its weight in gold if/when someone stumbles across this kind of problem.
I do have one request and one question…
Request
Any chance of moving “>= Xcode 16” to the preferences? I would imagine this won’t be changed too often and is a bit of an eye sore.
Question
Can you speak to how you actually put the “>= Xcode 16” in the menubar? Assuming it’s some kind of declare here with a MouseDown event.
We started there. The feedback I’ve gotten so far is that people with multiple projects are having to switch quite often. I suspect the answer is that this feature will be moved or completely disappear once it’s no longer an option, which will most-likely happen in the spring when Apple makes the iOS 18.x SDK mandatory and thus Xcode 16 will also be.
Also, remember that this tool may not only used by people who use Xojo.
That allows me to enter all of the details. I’ve configured the API access but it still refuses to action anything when I hit save. Nothing at all happens, just shows the clicking action but nothing saved or removed. Only cancel closes the dialog. The Team API is saved and works with Apple, however the email address is not updated.
When it was asked for access to the server password it was granted.
There are two things you can try. First, locate the keychain item in the Keychain Access app by searching for “Apple Profile Triage.” Then I suggest:
Open the item by double-clicking on it
Click the Access Control tab
Make sure Apple Profile Triage.app is in the list of applications that are always allowed access.
Close the keychain item window to save the changes
Open APT and see if you’re still getting errors when saving. If not, you’re done.
If so, try deleting the item named Apple Profile Triage from keychain altogether.
Note: If you’re running macOS 15 Sequoia, Keychain Access has been moved out of the Utilities folder into '/System/Library/CoreServices/Applications/Keychain Access.app'
“Apple Profile Triage” does not appear within Keychain Access. I looked through there last night in search of anything related to APT. I’ve tried searching both the full name and the abbreviated form. I can find nothing.
I was aware of the Sequoia move, quite annoying for one reason or another.
Its that time again, my certs expired.
Ive created and downloaded everything I can think of, and nothing works.
This happens every time I need to renew certificates.
Xojo will build the app but (something) complains that a certifcate is not included, or no profiles are available, or something else.
Ive tried using APT to give me a clue for the last 3 hours to no avail, and the package option just gets me this:
Surely there must be a step by step
get THIS, THIS and THIS guide to follow?
APT toggles between everything black, and everything red.
I delete all the red stuff, generate new, fail,
ask APT to sort it out/download/package and I get a screen of red again.
Hopefully this will make things clearer. I’m not talking about wildcard certificates here because they just make things more complicated IMHO.
For each application, you have up to 6 of these parts:
Application Identifier
Test Devices
Developer Certificate, expires 12 months from issue, 1 per developer on your team
Distribution Certificate, Expires 3 years from issue, 1 per application
Development Profile, Expires 12 months from issue, 1 per developer team
Distribution Profile, Expires 3 years from issue, 1 per application
Now, the two types of profiles listed above have references like this:
Development
Distribution
Application Identifier
Application Identifier
Developer Certificates
Distribution Certificate
Test Devices
Development Profiles
When one of the items contained in a profile expires (certificates) or changes (devices), the entire profile is invalid. The easiest way to fix a bad profile is to fix the contained items first and then the profile.
For example, each year when your account cycles, you are given the opportunity to remove test devices from your account. If one of those devices was attached to a development profile, that profile would become invalid. The same goes for your development certificates. When they expire, so do the profiles that contain them.
To fix a development profile:
Select it from the list
Click the Edit button
Select any Development certificates that should be associated with the profile.
Add any new devices that you want to be able to test on.
Click the Save button
Distribution Profiles
Distribution profiles are a lot easier in that really the only thing that can cause an expiration is for your distribution certificate to expire. if it does, make a new distribution certificate and then update the distribution profile by adding the new certificate.
If you haven’t already, I suggest upgrading to 3.6.x and trying out the new Identifier Diagnostics tool. It will create a PDF report based on the identifier of the app you are trying to release and tell you which profiles use that identifier and which certificates and devices are attached to those profiles. If it finds any issues, it’ll highlight them and adds a page at the end that enumerates them for easy viewing.