This class of issues are known as runtime errors.
A few key principles about debugging are captured below: In addition, you'll often find yourself in the role of a coding investigator in order to understand where and why an app is crashing or not working as expected. Debugging MindsetĪs an Android developer, you'll need to cultivate a "debugging mindset" as well as build up defensive programming practices that make writing error-prone code less likely. Refer to our guide below and/or these debugging slides for more a detailed look at debugging crashes and investigating unexpected problems with your app. You know you have experienced a runtime exception when you see this in your emulator or device:ĭon't worry though! This is totally normal and there's a specific set of steps you can take to solve these. So presumably something needs adding to the Googleĭevelopers Console, but the documentation on that is as clear as mud.When building Android apps, your app is bound to crash from time to time or exhibit strange unexpected behavior. I know thw app is running as the Toast messages appear on the device but no map. Google Maps Android API: In the Google Developer Console ()Įnsure that the "Google Maps Android API v2" is enabled.Įnsure that the following Android Key exists: (same as in AndroidManifest)ĪPI Key: 0gKmWT-U09vi2HR6t4K8V1vyFi9CMReRLqqS41A Please see for how to correctly set up the map. There are red messages in Logcat such as: Authorization failure.
I have no google_maps_api.xml files anywhere. I have a realĭevice connected via USB cable. I have run Keytool on the debug.keystoreĪnd have a valid API key from Google which is in the AndroidManifest (name=".v2.API_KEY"). I am only getting a blank screen, with Google at the bottom, and no map or tiles.
0 kommentar(er)
