37edc96d50
Getting a working mobile-SDK key from 2GIS turned out to require a sales-mediated B2B process (Platform Manager subscription, demo keys explicitly excluded from mobile SDK use per their own docs), not a quick self-serve signup. Swapped to osmdroid instead: free, no API key or account, works immediately. CityMapView (replacing DgisMapView/DgisSdkProvider) wraps osmdroid's View-based MapView via AndroidView, forwarding lifecycle events, with markers for the user's location and each nearby place. Configured required OSM tile-usage-policy user agent + app-private tile cache in GuideCityApp. Removed the now-unused DGIS_API_KEY plumbing and the arm64-only ABI filter (osmdroid has no heavy native libs, so it's not needed) — APK is back down to ~19.6MB from ~69MB. Verified: testDebugUnitTest passes, assembleDebug produces a working APK, sent via the Telegram bot (previously blocked by its 50MB limit with the 2GIS build). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
11 lines
662 B
Text
11 lines
662 B
Text
# Copy this file to local.properties (gitignored) and fill in real values.
|
|
|
|
sdk.dir=/path/to/your/Android/Sdk
|
|
|
|
# Base URL of the guideCity backend API. Options, in order of preference:
|
|
# 1. Nginx-fronted HTTPS domain (works from anywhere, not just the LAN):
|
|
API_BASE_URL=https://guidetest.vrubel.xyz/
|
|
# 2. Emulator -> host loopback: http://10.0.2.2:8000/
|
|
# 3. Physical device on the same Wi-Fi/LAN -> your machine's LAN IP, e.g. http://192.168.1.50:8000/
|
|
# (backend already binds 0.0.0.0:8000 via docker-compose, so it's reachable on the LAN IP with
|
|
# no extra config; cleartext HTTP is allowed in debug builds only, see app/src/debug/AndroidManifest.xml)
|