-
Notifications
You must be signed in to change notification settings - Fork 24
fix(explore-dash): stop per-foreground IP geolocation lookup #1055
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
QuantumExplorer
wants to merge
1
commit into
develop
Choose a base branch
from
fix/geo-restriction-drop-ip-lookup
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+37
−84
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: dashpay/dashwallet-ios
Length of output: 19767
🌐 Web query:
Apple StoreKit Storefront.updates behavior countryCode changes documentation💡 Result:
In StoreKit 2, the
Storefront.updatesasynchronous sequence is the recommended mechanism for listening to changes in the App Store storefront, including updates to thecountryCode[1][2][3]. Key points regarding its behavior include: Official Documentation: TheStorefront.updatesproperty is an asynchronous sequence that emitsStorefrontinformation whenever the system updates the storefront [4][2]. Apple advises that because the storefront value can change at any time, apps should monitor this sequence and respond to changes (e.g., by refreshing the list of available products) [1][2]. Usage: You should listen to this sequence to detect when a user changes their App Store region or switches Apple ID accounts [5][6]. When a change is emitted, you can access the updatedcountryCodefrom the emittedStorefrontobject [5][7]. Known Limitations and Issues: - Sandbox Testing: In the sandbox environment, switching accounts can sometimes fail to trigger updates or result in stalecountryCodevalues due to caching or system-level bugs [8][9]. Developers have reported scenarios, particularly in certain iOS 18.x versions, wherecountryCodedoes not synchronize after switching sandbox accounts in settings [8]. - Best Practices: If you encounter issues with stale values, ensure you are fully signed out of the previous Apple ID in the system settings and signed into the new one [9]. In production, the API is generally reliable, but developers should always build their apps to handle storefront changes dynamically by reacting toStorefront.updatesrather than caching the storefront value indefinitely [2][10]. Legacy APIs: TheSKStorefrontCountryCodeDidChangeNotification(used with the older StoreKit 1SKPaymentQueue) is considered deprecated in favor of usingStorefront.updates[3]. Top results: [4], [8], [2], [10]Citations:
🏁 Script executed:
Repository: dashpay/dashwallet-ios
Length of output: 312
Subscribe to App Store storefront changes.
When storefront resolution sets
hasCheckedRestriction, later checks do not re-readStorefront.current. ObserveStorefront.updatesand update the restriction status for each newcountryCode. Add coverage for a storefront-only resolution followed by a storefront change.🤖 Prompt for AI Agents