Posts

Post not yet marked as solved
4 Replies
0 Views
Update: After the official release of Xcode 13.0, my builds are working.
Post not yet marked as solved
4 Replies
0 Views
Post not yet marked as solved
4 Replies
0 Views
Update: I have tried a whole lot of things ... without any success. Even took the route of trying to install RVM and libffi directly
Post not yet marked as solved
12 Replies
0 Views
I am seeing the same issue ... seems like the online manual creation of an identifier via the `Certificates, Identifiers & Profiles` page does not allow the maccatalyst prefixed name.
Post not yet marked as solved
2 Replies
0 Views
See the 2019 WWDC sessions on Core Data and CloudKit - There are new capabilities to do sync.
Post not yet marked as solved
1 Replies
0 Views
See this other thread ... https://forums.developer.apple.com/message/363865#363865
Post marked as solved
4 Replies
0 Views
Quinn -Okay, I am able to create an archive. I had two targets that used just about all the same *.swift files (79 total). One target worked, the offending target did not. So I reordered the files one by one in the target that did not archive to match the target that did Archive. Eventually, it was able to create the archive.Thanks.
Post marked as solved
4 Replies
0 Views
Quinn -Thank you for your response.I also created a test project, included all the imports, included the complete file that I am having the issue with. I was able to create an Archive without issueI also removed the file from the project, then added it back into the project. Still had the issue.I removed the DerivedData directory and also cleaned the project and folder. Still had the issue.I restarted Xcode. Still had the issue.Within the file itself, I removed the UITextField, and replaced that code segment with a UITextView to see if it was an ordering issue, and it did not fail. When I put it back in, it fails.Thanks.
Post not yet marked as solved
9 Replies
0 Views
Update: Production public database data has started to repopulate - I see records going back till January 2017 now.BUT - we do not see the any of the `Users` records repopulating, and do not see any of our test data out test production private databases.