It's kinda fun. Like the Sphinx Gate in Never Ending Story. I think I got it all figured out. Get lit up. I do think looking at what other apps did is a bad idea as they update these guides often and older apps will be grandfathered in until their next update. So you are adding an unnecessary complication by doing that. I had to add stuff to my subscription menu I've never seen anyone else do. It was helpful info to the user though. They aren't tech support and stop at the first issue. So I had several rejections before I found a SO post detailing all of what they expected to see there. Finally it went through.

Try restarting XCode.

So far, I've found the public testflight to be mostly worthless. The stats don't change. They seem stuck from maybe day one or two. My app requires Game Center and yet only one new name is on the board despite 70 users with various session numbers. Do users hate Game Center and maybe reject the app for that? That would be some legit info. Nearly 20 appear to be squatting on the "accept" since the start. But I can't really boot them because Apple says these stats can take 72 hours to update. Which I don't understand either. Daily updates would seem painfully slow for testing. 72 hours is an eternity. I also understand why users would be anonymous but some tag could be used so you know Anonymous 1 activity from Anonymous 2. They are just all in the pile other than by device. I do know that the crash number is total since their first use. So if they started on build 0, on build 20 will reflect all crashes 0...20. I do think you can expect a serious fall off. I've used public testflight links myself and even apps I think were fine, there wasn't much useful feedback I could provide and I don't really return to them. I expect a lot of churn for mine as well. But even considering that, the stats are odd.

I think I found the real issue. It does this when breakpoints are activated regardless of if no actual breakpoints are active.

No. It can be disabled on Connect but is enabled by default. They just aren't very chatty. We need some kind of reward/bribe system. Like feedback enters a lottery for Apple gift cards or something.

I get the same errors on files that are no longer in the project, not loaded, not mentioned anywhere in the code, and not part of any SCN or OBJ. But all are related to roughness textures. Although no roughness textures in use are causing an error.

That is the kind of error I see when I have two files of the same name. Usually images for materials. So I would guess you already had a PrivacyInfo.xcprivacy in the project when you added one for the tutorial.

Although I don't see it here, mine was getting the same reports until I removed an extra empty item. Apparently I inadvertently hit a plus button in the property list. I read in this forum that it could cause an issue and it does. The only difference I see from mine in Privacy Accessed API types is that I have DDA9.1 in the reasons for the time stamp.

if let myTest = UserDefaults.standard.value(forKey: "alreadyShownToUser") as? Bool{ } UserDefaults.standard.set(isProtected, forKey: "alreadyShownToUser") But instead of the string, I use an enum to prevent typing errors and make it easy to remember.

I've not experience that with UserDefaults. I wouldn't give up on finding that issue. But anything I want protected in cases where a user might lose or change their device, I use CoreData with NSPersistentCloudKitContainer. Which is easy to remember if you watch this video as this Nick Gillet says it 1.5 times per minute.

Unless it is a trademarked logo, I think the only way to help is to design a new logo for you. If it is trademarked then I would assume they would then approve yours and cause the others to get rejected. It may be possible that another developer raised the issue. If your use is first, you may have options against the holder's trademark but I'm not a lawyer.

This sounds more like a job for Model I/O than Metal? It already has voxel routines. Unless you are doing it all from scratch.

Yes, you can test and TestFlight achievements without them being live. That error is saying you have the app referring to the wrong or mistyped ID. Should be the Achievement ID and not the reference name. let progress = min(percentComplete, 100.0) let achievement = GKAchievement(identifier: achievementID) achievement.percentComplete = progress achievement.showsCompletionBanner = true // Optional: to show a banner when completed // Report the achievement progress to Game Center GKAchievement.report([achievement]) { error in if let error = error { print("Error reporting achievement: \(error.localizedDescription)") } else { print("Achievement reported successfully") } }

I think I answered that wrong. I somehow thought "Trader" meant using apps as a storefront rather than selling the app itself. So a clothing store, stocks, etc. But maybe anyone selling apps or IAP is a "Trader". Although if true, that would seem to be better guidance than whatever was given.

It shows up if you remove the space, use an underscore or dash, or surround it with quotes. I have no idea why it won't list it using the title as is. Have you tested listing the name this way as a keyword? I wouldn't think it would be necessary but it might act as a patch until you get a better answer. It may take a day or two to index the new keyword although I have no idea if it takes any time at all.