Open HelmiAshraf opened 1 month ago
@HelmiAshraf Why was appStoreListingURL empty in this case? Since appStoreListingURL was empty, what are your expected results? (Also, if you can provide the entire upgrader log that might be more helpful.)
Case 1: Wrong Country Code with Malaysia (English US)
When the device is set to Malaysia and the language is English (US), the upgrader package incorrectly detects the countryCode: US
instead of MY
and current locale: en_US
instead of en_MY
. This prevents the app from retrieving the correct App Store listing.
Steps to Reproduce:
Expected Behavior: The app should detect the country code as MY and retrieve the correct store listing.
Actual Behavior: The country code is detected as US, and the store listing cannot be retrieved.
Case 2: ActionKit Errors with Malaysia (English UK)
When the device is set to Malaysia with English (UK), the country code is correctly detected as MY
, and the store listing is retrieved successfully. However, the logs are filled with ActionKit
conversion errors related to <private>
parameters.
Steps to Reproduce: Set the device to Malaysia with English (UK). Run the app. Observe that the correct country code (MY) is detected, and the store listing is retrieved, but ActionKit errors appear in the logs.
Failed to index parameter type: <private> in is.workflow.actions.encodemedia: Error Domain=(extension in ActionKit):__C.WFParameter.ToolKitConversionError Code=0
Device Information: iOS Version: 18.0 Upgrader Version: ^11.1.0 Flutter Version: 3.24.2
I am seeing a similar issue in production, but cannot reproduce in testing. I live on the French/Swiss border, so maybe localisation is an issue. How can I print out which store upgrader is trying to access, so that I can complete my issue report.
The upgrader popup shows perfectly in both French and English (depending on the phone settings) with the latest release notes. But when we click on the upgrade now button, nothing happens.
Galaxy A53 5G (my wife's Samsung has the same issue) Android version 14 Upgader version:^11.1.0
This issue is observed on iOS 18, while it works fine on Android and iOS 17 or below.
Steps to reproduce: