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.

For direction and distance, it needs GPS data in this case. And that accuracy is largely outside of Apple's control. It's looking for two points for a direction vector and if the second is within three meters of the first, it's only seeing the one point. Yes, while it might not work for one flight, as long as you get data to establish the user is climbing or descending, you could extrapolate what the step data means. The API uses this to determine if the user is taking the steps or using an elevator. You could also take the start and end GPS data directly and apply your own analysis of what is occurring between these points. But this 3 meter accuracy will still be an issue. The device is capable of obtaining a more accurate picture of its surroundings but then that's not really practical for your case. You probably don't want the user to start their exercise by doing a room scan. It's the old trade off of speed/accuracy/convenience. I'd try to determine how sensitive it really is by looking at the raw GPS data. You might get by with some trick like having the user press start with the device on the floor. Or just explaining to the user the need to move further or otherwise show them when they hit a new GPS point to qualify them.

According to this, "A single floor has a height of approximately three meters". So that would make me think that anything falling under that tolerance is ignored. This is also approximatley the limitation of the GPS data itself and I think it is less accurate vertically. My brother and I walk about 10-12 miles a day on vacation and my phone always gives me more credit than his despite no real difference in where we go. I'm not exactly sure why. I do tend to do the navigating and he mostly keeps his in his pocket. I think the data can only be used to track your own relative performance than be accurate enough to compare to others. If Apple's Fitness app isn't picking up the difference either, I'd say it's just a limitation. It wouldn't surprise me if you went one floor and didn't get credit for it but two floor and got credit for both as that would form a trend over two points.

I’ve not used this API but it appears to keep track of historical data and doesn’t require active monitoring from the app? Unless I’m reading this wrong. It looks like you just need a timer and then if the app is shut down, pass the remaining time to a push notification to alert the user. Even if it could be done as a background process, the user has the option to turn that off. If they don’t understand why or forget, they may do that.

I‘m currently working on polishing my SceneKit game. I mainly stuck with SceneKit because I have years of experience working with it and thought I could compensate for any issues faster than learning something new. I even felt like it was a smart idea after Unity’s recent controversy. You can feel somewhat alone in figuring things out. If you want to cross platform, that’s a solid point for Unity. Mine is made for the iOS mobile platform in mind. So I didn’t care about that. That said, and especially if this flops hard, I might try a Unity or Unreal PC game next.

You can get it to work in SceneKit but not RealityKit? I misread the question and thought it was Scenekit related where I do have it working. The doors are animated although the orientation is wrong. Y-axis is up yet this is on Z. I haven't used realitykit enough. The error may be related to RealityKit catching this difference in orientation? Not sure why it would care though.

You need a texture source as well. Mapping the UV to this custom mesh. SCNGeometry(sources: [vertexSource, normalSource, textureSource], elements: elementArray). Makes one appreciate Blender.

There is an option to submit a video for the review. I got rejected once because they thought my app was only running an animation and also because it didn’t use ARKit enough. So I made a video showing how the user is creating the animation and that ARKit is an option to help the user visualize solutions. I think they were more accustomed to AR apps being all AR environment. Regardless, the video seemed to clear up any confusion. They deal with a flood of apps and can’t spend all day figuring out one and it may be a topic outside their interest, so its good to make things fast and simple to understand.