It will take a day to see anything. Its not something you can check hourly unless they changed something in the last year.

I would take that to mean nothing observable occurred after purchase. It should popup with a notice that the purchase was successful. I always add either an additional “Thank You” or change something in the UI to indicate the purchase.

I haven’t implemented this, but I think you can detect if a user has refunded IAP. You can check for refund abuse and should be able to prevent them from purchasing another IAP. I don’t know the rules for implementing such a function and haven’t tried this myself. I just remember checking for it on a subscription app.

Good testers are hard to find. Would be nice if there was some way devs could reward anonymous public testers or put some kind of bounty on finding issues. Like apple app store credit that could deal with international users.

It has been a little annoying to me how the technologies fork and then you have parallel paths to the same thing but with different obstacles in the paths. I haven't even had a chance to touch SwiftData. It's tough to try to master something before the replacement is introduced. The nature of tech, I guess. But CoreData has NSPersistantCloudKitContainer where the databaseScope can be set to public. I followed this video and it works great for my use case and scale. Although I would think a typical social media app would be more server side intensive and require server side logic.

In sceneKit, you can just build your physics shapes from other shapes when all else fails. So the couch collision shape could be explained with a few boxes using SCNPhysicsShape(shapes:. I don't think RealityKit has that yet. But I could be wrong.

You can require certain hardware for your app. UIRequiredDeviceCapabilities. You can also check supportsSceneReconstruction. RoomPlan has a test as well I think. RoomPlan features won't work without lidar. But no, its inclusion alone would not prevent the app from opening. So you can have an app that has that as a feature but may have a broader set of features important to those who don't need to use the LiDAR portion.

I haven't had a chance to dive into Metal. I've only played with it. It's for low level GPU stuff. You won't need to use it to write a game unless maybe writing the whole engine. SceneKit has all the tools to create a 3D game. It doesn't get many flashy updates if any. It is not cross platform, doesn't have the community of a dedicated game engine, and so you'll need to hack through more things yourself. But you can program in Swift, easily incorporate all of Apple's API's, and there is no additional fee to use it. Do a search for Fox or Fox 2 and you'll see Apple's example as well as what others have done with that example. That should get you started. You might also want to look at Godot, Unity, and Unreal.

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.