You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let Google Maps SDK specify the version for com.android.volley: The version used for com.android.volley was sepcified in tbxml-android.gradle manually to 1.2.1. This was needed when using the old Google Maps SDK com.google.android.libraries.maps:maps:3.1.0-beta which pointed to version 1.1.1 and which was no longer available online. Since the latest Google Maps SDK is used, it will point by itself to a more recent version.
Copy tbxml-android.aar only once: tbxml-android.aar was copied to two paths: app/src/main/libs and app/src/main/app/src/libs. The second copy was useless and also wrong. Use the first path only.
Remove unnecessary repositories from tbxml-android.gradle
The default repositories for google and mavenCentral are already defined by cordova-android
Removes a gradle warning: Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0, because url 'https://maven.google.com' would have to be url = 'https://maven.google.com'
Remove compileSdkVersion and packagingOptions from tbxml-android.gradle
compileSdkVersion is set by cordova-android
Removed packagingOptions for excluding README and LICENSE. This should not be done here and it is not sure if this works and will bring a benefit.
Don't use flatDir in tbxml-android.gradle: Using flatDir produces the warning Using flatDir should be avoided because it doesn't support any meta-data formats.. Instead android source sets will be used.
iOS
Upgrade Google Maps SDK from version 9.3.0 to 10.0.0
Use Metal renderer also for simulator instead of OpenGL
Remove WebKit redraw hack
Removed document.body.style.transform = 'rotateZ(0deg)'; from Map.js from Map.refreshLayout and Map.setDiv, which was used to for force WebKit browsers to perform a repaint/redraw, because in older WebKit browsers (Safari, early Chrome), certain DOM manipulations or CSS changes wouldn't trigger a visual update immediately, causing rendering glitches or elements appearing "stuck" in their old positions.
This fix is no longer needed in modern WebKit Browsers and caused issues on Chrome on Android, see #19