config: fix IAB package name + flatten Production Iab example
- appsettings.json + docker-compose default: PackageName com.bargevasat.hokm → com.bargevasat.app (the validate API URL embeds it; wrong value breaks Bazaar/Myket token verification). - appsettings.Production.json.example: Iab keys were nested (Iab.Bazaar.*, Iab.Myket.*) which don't bind to the flat IabOptions; flattened to PackageName / BazaarClientId / ... / MyketAccessToken. MyketAccessToken is already wired end to end: ENV_FILE IAB_MYKET_ACCESS_TOKEN → compose Iab__MyketAccessToken → IabOptions.MyketAccessToken → VerifyMyket. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
+1
-1
@@ -57,7 +57,7 @@ services:
|
||||
Zarinpal__CallbackUrl: ${ZARINPAL_CALLBACK_URL:-http://localhost:1505/api/coins/pay/callback}
|
||||
Zarinpal__ClientReturnUrl: ${ZARINPAL_CLIENT_RETURN_URL:-http://localhost:1500}
|
||||
# Store in-app billing verification (Cafe Bazaar / Myket) — fill from panels.
|
||||
Iab__PackageName: ${IAB_PACKAGE_NAME:-com.bargevasat.hokm}
|
||||
Iab__PackageName: ${IAB_PACKAGE_NAME:-com.bargevasat.app}
|
||||
Iab__BazaarClientId: ${IAB_BAZAAR_CLIENT_ID:-}
|
||||
Iab__BazaarClientSecret: ${IAB_BAZAAR_CLIENT_SECRET:-}
|
||||
Iab__BazaarRefreshToken: ${IAB_BAZAAR_REFRESH_TOKEN:-}
|
||||
|
||||
Reference in New Issue
Block a user