If the range restriction is with peer-to-peer WiFi, then perhaps consider using WiFi, but not peer-to-peer, with a battery-powered router half-way between the two iPhones?

You should take ownership of your app. Use your Apple Developer account, and add your Developer as a member of your Team (with an appropriate role). (If the app already exists under another account, then it will need to be transferred.) Use your GitHub (or equivalent) source code repository, and add your Developer to that. So everything is hosted/sourced on an account that you control.

"self" refers to the object that the func is contained in. But your code shows no such object. Perhaps you have you omitted the crucial code? ...but if these funcs are global, then there is indeed no "self".

If updates aren't stopping, that suggests something like (one of): • You aren't stopping them • They are immediately restarting • They are starting multiple times You need to call stopDeviceMotionUpdates() Which you do, in stopQueuedUpdates() So are you calling stopQueuedUpdates() correctly (you don't show the code for this)? Do you have only one WatchMotionManager?

Your source code is not uploaded to the App Store, so Apple will not be looking at those warnings. There are different views on it: Some people treat warnings the same as errors - they must be fixed. Other people take a more relaxed view - some warnings are trivial, and cause no harm. My personal approach is to allow some warnings during development (e.g. when using TestFlight), but I like to clear them all before submitting to the App Store.

You are receiving data, and the "let data = data" command is okay. So presumably the failure occurs on: if let decodedResponse = try? JSONDecoder().decode(FDCResponse.self, from: data) { You don't include a definition of FDCResponse, so I can't test that. However, you can try what I did: if let data = data { if let dataString = String(data: data, encoding: .utf8) { print("got dataString: \n\(dataString)") } // ... Which prints the incoming json, which looks like this: {"totalHits":5,"currentPage":1,"totalPages":1,"pageList":[1],"foodSearchCriteria":{"dataType":["Foundation"],"query":"apple fuji","generalSearchInput":"apple fuji","pageNumber":1,"numberOfResultsPerPage":50, ... So you can compare that json with your FDCResponse, to see where an error might arise.

https://developer.apple.com/programs/enroll/

No. Unless you have specific reasons for using Betas, you should stick to release versions. Betas are less reliable, consume more resourses, have poorer battery life, and some apps may have issues. Update to the release version of iPadOS 15, when that becomes available.

To leave a team From App Store Connect: Click your name (at the top-right), and select "Edit Profile" Check it's the team you want to leave Scroll to the bottom, and select "Leave Team" Confirm

Compiles cleanly, and runs fine for me. M1 MacBook Pro Xcode 12.5.1 (12E507) I suggest you try the usual fixes... clear the Derived Data folder, restart everything...

On tapping "Fake data realtime update": you start an infinite loop of updataData() which calls itself (100 times a second) For me, this pins CPU activity at 100% Considering that, I found your code surprisingly responsive, I expected it to grind to a halt! Updates may be arriving rapidly, but does your UI really need to update 100 times per second? I think in a real app, a more realistic strategy would be to gather a batch of updates, and update the UI once, with the entire batch. And of course, non-UI work need not be on the main thread.

Did you check both websites? App Store Connect Apple Developer

From what you have posted, you have: App bundle id: • com.legacylouisvillellc.legacylouisville ...and extension id: • com.legacylouisvillellc.legacylouisville But these two bundle id's must be different. The extension's bundle id should use the app's bundle id as a prefix, so... App bundle id: • com.legacylouisvillellc.legacylouisville ...and extension id: • com.legacylouisvillellc.legacylouisville.myExtension (Whatever myExtension should be called)

Annotations rely on CLLocationCoordinate2D. You will need to convert your Eastings and Northings to Longitudes and Latitudes. How you do this will depend on how you have defined your Eastings and Northings.

Geofencing... isn't this what Region Monitoring is for? https://developer.apple.com/documentation/corelocation/monitoring_the_user_s_proximity_to_geographic_regions