Posts

Post not yet marked as solved
1 Replies
0 Views
As a followup - this appears to only be true for macOS Catalyst apps. It looks like UIPrintInteractionController and UIPrintInfo also got sucked into this mess as well? Are these truly not allowed for macOS Catalyst now?
Post marked as solved
24 Replies
0 Views
I was in the process of setting up a new automated build this morning and started getting this error message too. Same scenario - I'm trying to upload both an iPadOS and Catalyst version of my app with the same build numbers. I'm using the xcrun altool command line tools to upload my builds. *** Error: Error uploading '<My App>'. *** Error: The bundle version, 1, must be a higher than the previously uploaded version. Duplicate bundle version. (-19210)  {     NSLocalizedDescription = "The bundle version, 1, must be a higher than the previously uploaded version.";     NSLocalizedFailureReason = "Duplicate bundle version.";     PreviousBundleVersion = 1; }
Post not yet marked as solved
57 Replies
0 Views
For what it's worth - my project has a similar hierarchy of frameworks being built.
Post not yet marked as solved
6 Replies
0 Views
Update: I was able to work around this by EITHER changing my Optimization Level in Release to "No Optimization" OR by changing Compilation Mode from "Whole Module" to "Incremental".
Post not yet marked as solved
6 Replies
0 Views
I'm having this issue too - both my macOS and iOS projects. It's hanging on a "Compile Swift source files" step. It's also happening on Swift 4.2 and Swift 5.
Post not yet marked as solved
16 Replies
0 Views
I noticed the same problem yesterday - assume it is a widespread bug? I'm hoping for a fix soon.
Post not yet marked as solved
2 Replies
0 Views
These controls already had this done in the initializers - no luck.
Post marked as solved
3 Replies
0 Views
Hey OOPer,Thanks for the workaround, that works great. I tend to forget most of Apple's SDKs support KVO. Now I just need to make sure to remember to clean that up around release time.Now that you've confirmed it isn't just my going crazy, I've submitted the bug report too :-) Hopefully it gets fixed before the gold master is locked down!