The iOS & Apple Watch apps are ready, but we’re hitting a "CI"
Hello everyone,
I have some news to share regarding the iOS and Apple Watch companion apps for PawseKeys.
The good news? The apps are fully developed and ready to go! However, I’ve hit a technical roadblock with my CI (Continuous Integration) pipelines. I’m seeing some cryptic errors during the build process that I haven't been able to resolve on my own, so I’m currently working with Apple’s support team to get these pipeline issues cleared up.
Because I want to ensure the version that reaches your devices is stable and correctly signed, I’m delaying the mobile unlock features just a bit longer while I wait for this fix.
In the meantime:
You can still fully enjoy the desktop features: one-click locking, timed locks, and "pet-proofing" your keyboard.
PRO Users: These mobile updates will be 100% free for you the moment the pipeline is cleared.
Track Progress: I’ll keep you posted on the latest at https://pawsekeys.app.
I’m doing my absolute best to get past this "Apple gatekeeper" and get these apps to you. Thank you so much for your patience and for all the love you've shown PawseKeys so far! ❤️



Replies
Is this happening on every build or intermittently?
Did anything change recently in your pipeline setup?
Are you using Xcode Cloud or a custom CI setup?
Are you able to reproduce the issue locally?
Did previous builds work fine before this?
Is the error message giving any useful clues at all?
I personally like the transparency here. Shipping ready code blocked by infra is way more common than people admit.
Pablo, the transparency here is really good. Most solo founders would just go quiet while dealing with a CI mess and hope nobody noticed the delay. You turned it into a proper update with context, which builds more trust than a clean launch would have.
Apple's code signing and CI pipeline issues are one of those things that look simple from the outside until you are in them. The cryptic errors especially. Fingers crossed the Apple support team moves fast.
One thing that might help if you have not tried it already: Fastlane with manual signing as a fallback tends to be more predictable than Xcode Cloud for edge cases. Might be worth a look while you wait.
Good luck on getting it across the line.
PawseKeys
PawseKeys
Hello everyone,
I finally submitted the iOS version (which was not originally planned) because Apple didn't accept my standalone watchOS version. I replanned the project as they asked to have a companion iOS/watchOS app; I now have an iOS version tested and available on TestFlight.
Regarding the watchOS version, it is failing during the upload process with error codes 65 or 70. This doesn’t make any sense because the certificates and profiles are correct, and it works perfectly locally I can even generate the .ipa or .xcarchive files without issues. I’ll share the logs with Apple Support to see if they can finally help with this.
Thank you so much for your support, fam.
PawseKeys
Have you ever went through that guys?