Search results for

Apple Maps Guides

151,844 results found

Post

Replies

Boosts

Views

Activity

URGENT: App rejected for "manual check-in" requirement not in Guidelines 5.1.2 — built feature anyway, still waiting (APP LAUNCH, BANGKOK dependency
Our solo traveler safety app has been rejected multiple times; for random reasons. Latest rejection demands manual check-in each time for location display — this requirement doesn't appear in published Guidelines 5.1.2 or 5.1.5. BUT!! We built the feature anyway: users invisible by default, must tap Check In to appear on map, auto-expires 24hrs. Submitted video proof, screenshots, detailed notes. Age rating set to 18+. (its not even adult but we did it anyway as to match our own policy) Comparable apps (Couchsurfing, Life360, Snap Map) approved without this requirement. Time-critical: investor meetings Bangkok Dec 11, flight Dec 10 11pm GMT - 15 months development. UK registered company. Has anyone dealt with unpublished requirements being applied inconsistently? Any advice appreciated - I cant get through to dev/app review team or senior advisors. And lovely call handlers in cork tried his. best but cannot do anything - ive not slept for near 24 hours due to unknown reasons - some minor mak
3
0
80
1w
Reply to RFID read
Two questions please: I understand silently reading NFC tags using NFC libraries is not possible. Is there perhaps a different library which allows reading other types of RFID tags? Is there a way for a company to request silently reading NFC tags on the condition that the relevant app only be deployed internally, never on the apple store? Thanks
Topic: App & System Services SubTopic: Drivers Tags:
1w
Reply to SpriteKit framerate drop on iOS 26.0
Apple sent this response on 18 November 2025: We believe this issue has been addressed. Please verify this matter is resolved after updating to iOS 26.2 beta 3. iOS 26.2 beta 3 (Build: 23C5044b) Posted Date: November 17, 2025 In my testing, the issue seems resolved indeed! Thank you! It is great and encouraging news for SpriteKit users. The issue FB20808104, where both SpriteKit and RealityKit drop frames under SwiftUI views, still holds. I will continue to look for updates on the Feedback Assistant.
Topic: Graphics & Games SubTopic: SpriteKit Tags:
1w
Reply to URGENT: App rejected for "manual check-in" requirement not in Guidelines 5.1.2 — built feature anyway, still waiting (APP LAUNCH, BANGKOK dependency
Guys pls! East Coast - someone. Flight in 48 hours. Built every feature requested including manual check-in system that isn't even in the published guidelines again it's over 15M of dev work in the bin! We're a registered business. Investor meetings depend on this, partnerships but also our target market initial. If any Apple employee sees this - pls, please look at our submission. We've exceeded every requirement. Video proof, screenshots, everything documented. App ID: 6742558238 Any help appreciated! You have my details I permit you to call and email or whatever you need to do; I consent. Thank you. Neil Saeed
1w
Reply to XCode Enhancement Request... The ability to Obfuscate Builds
If you'd like Apple to consider adding the functionality you have described, please file an enhancement request using the Feedback Assistant. If you file the request, please post the Feedback number here. In this case since you have suggested a number of separate ideas I recommend filing a separate enhancement request for each one instead of lumping them all into one. That way each can be considered separately. Also, please review Apple's Unsolicited Idea Submission Policy. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?
1w
XCode Enhancement Request... The ability to Obfuscate Builds
Hi... It would be nice if Apple / XCode would be so gracious to explore the possibility of providing the ability to include: Code scrambling / renaming Control-flow obfuscation String encryption Anti-debugging Anti-hooking Jailbreak detection App integrity checks Runtime tamper detection That way, we could eliminate the need to settle for third-party software. Who do we have to bribe to submit such a request and entertain such an idea?
1
0
97
1w
XCFramework with Common Third-Party Dependencies Causing Duplicate Symbol Conflicts
What is the recommended approach for distributing an XCFramework that uses common third-party dependencies (like Google Maps) when client apps may also use the same dependencies, resulting in duplicate symbol conflicts? I'm developing a closed-source SDK distributed as an XCFramework. My SDK internally uses Google Maps for mapping functionality. However, when clients integrate my XCFramework into their apps that also use Google Maps, we encounter duplicate symbol errors. What I've Tried: Static vs Dynamic Linking: Both approaches result in conflicts Static linking: Google Maps symbols compiled into my binary Dynamic linking: GoogleMaps.framework bundled with my XCFramework Build Configuration: Set Build Libraries for Distribution = YES Tried various linking strategies Architecture Changes: Used @implementation_only import Wrapped code with #if canImport(GoogleMaps) However, the dependencies still get linked at build time
9
0
314
1w
Reply to XCFramework with Common Third-Party Dependencies Causing Duplicate Symbol Conflicts
[quote='868615022, Charita, /thread/805901?answerId=868615022#868615022, /profile/Charita'] It would be helpful if you could suggest a way in which this can be handled at my end. [/quote] I can suggest various options, but there are no good options here. I outlined the reasons for that in my previous post. Ignoring all the build-time stuff for the moment, let’s focus purely on the runtime aspects. You only want one version of this vendor’s code in the client app’s process. Where should that code be? If you statically link it in your framework then the client can’t access it in the normal way. If the client statically links it into their app then your framework can’t easily access it. There’s no standalone framework available from the vendor, so that’s not an option. I see three potential options: You statically link the code into your framework and provide the necessary infrastructure for the client to access it from there. You create a standalone framework from this code, ship it to your clients, and have bo
1w
Reply to Certificate revocation check with SecPolicyCreateRevocation/SecTrustEvaluateWithError does not work
[quote='868450022, DTS Engineer, /thread/808875?answerId=868450022#868450022'] This gels with my understanding of how things should … work [/quote] Actually, that understanding was wrong. It seems that things only end up on Apple’s ‘naughty’ list if they’re revoked for the right (well, wrong) reasons, specifically, for compromised keys [1]. So, to test this stuff you need to check a certificate that the system really thinks is revoked. A good example is this: https://global-root-ca-revoked.chain-demos.digicert.com/ Using that I crafted a small test program that gets a server’s certificate chain and checks it for revocation. The code is at the end of this post. When I run this on macOS 15.7.1, I see this: will run task, url: https://example.com challenge NSURLAuthenticationMethodServerTrust will check chain did check chain, success: true did run task, status: 200, bytes: 513 will run task, url: https://revoked.badssl.com challenge NSURLAuthenticationMethodServerTrust will check chain did check chain,
Topic: Privacy & Security SubTopic: General Tags:
1w
Did Apple adjust ASO ranking factors? Metadata and rankings appear impacted.
Noticed a sudden drop in my keyword rankings recently and after some digging, it looks like Apple rolled out a major ASO update, which a lot of developers seem to be talking about. Curious if anyone has insights on what specifically changed - it seems like the app title may no longer hold the same weight in keyword rankings.
1
0
83
1w
Reply to Background fetch when app is forced quit
[quote='868602022, ygbykov, /thread/808088?answerId=868602022#868602022, /profile/ygbykov'] Apple may want to reconsider how it interprets users force-quitting apps. [/quote] If you want to get your “two cents” in front of the folks who have the power to enact change, I suggest you put them in an enhancement request. One of the reasons why these behaviours are not documented is that Apple reserves the right to change them. This has happened in the past, and it’s not hard to imagine it happening again in the future. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w