Menu Right

Top Social Icons

Responsive Full Width Ad

Left Sidebar
Left Sidebar
Featured News
Right Sidebar
Right Sidebar

Set Authorized Redirect URIs in Google API console

Once you have created your Google OAuth API Keys, you may be wondering how to authorize redirect URIs for your applications? or may you are receiving Error:redirect_uri_mismatch error. You can correct it by following these simple steps below.

Note: This steps are intended for novice users.
  1. Go to Google API console and click API Access tab on the sidebar.
  2. Click Edit Settings under Client ID for web applications block.
  3. Enter your URIs, one per line as shown in picture below, and click Save/Update.
That’s it, your application should work without any interruption from now on. For more info you can checkout google documentation here.

Creating Google OAuth API Keys and Developer Key

Google API lets you play with the core of Google system, by building queries, a client can access required data from various Google services, which can be used to build all types of Google based applications. Before sending API queries, a client application needs Google API keys. In this basic tutorial we will learn about obtaining Google API Keys and developer key from Google API console.

Create Client ID and Client Secret

  1. Sign-in to Google and go to Google API console,  click API Access on the left sidebar, click big blue button “Create an OAuth 2.0 Cliend ID“.
  2. A box should pop-up, enter your Project name and Product logo (optional), click next.
  3. Next choose your application type, usually it is Web application for websites.
  4. You should now be presented with Google Client ID and Client Secret on next page. You can use this information in your Google applications.


Creating Developer Key

Developer key is required to identify the project you’ve undertaken, such as you may be developing a custom Google Map or Analytics page etc. To keep track of its requests Developer Key is required. Let’s see how we can obtain Developer key for your project below.
  1. Click on Services link on left sidebar. Click on any status button to turn it on.
  2. Google Terms of Services page should appear on the next page, click accept button to proceed.
  3. Now go back to API access list by clicking API Access on the left sidebar. You should find another key listed below called Simple API Access. The API listed under it is your Developer key. Hope it helped, good luck.

Marshmallow Android 6.0


Whether you like them straight out of the bag, roasted to a golden brown exterior with a molten center, or in fluff form, who doesn’t like marshmallows? We definitely like them! Since the launch of the M Developer Preview at Google I/O in May, we’ve enjoyed all of your participation and feedback. Today with the final Developer Preview update, we're introducing the official Android 6.0 SDK and opening Google Play for publishing your apps that target the new API level 23 in Android Marshmallow.

Get your apps ready for Android Marshmallow

The final Android 6.0 SDK is now available to download via the SDK Manager in Android Studio. With the Android 6.0 SDK you have access to the final Android APIs and the latest build tools so that you can target API 23. Once you have downloaded the Android 6.0 SDK into Android Studio, update your app project compileSdkVersion to 23 and you are ready to test your app with the new platform. You can also update your app to targetSdkVersion to 23 test out API 23 specific features like auto-backup and app permissions.
Along with the Android 6.0 SDK, we also updated the Android Support Library to v23. The new Android Support library makes it easier to integrate many of the new platform APIs, such as permissions and fingerprint support, in a backwards-compatible manner. This release contains a number of new support libraries including: customtabs, percent, recommendation, preference-v7, preference-v14, and preference-leanback-v17.

Check your App Permissions

Along with the new platform features like fingerprint support and Doze power saving mode, Android Marshmallow features a new permissions model that streamlines the app install and update process. To give users this flexibility and to make sure your app behaves as expected when an Android Marshmallow user disables a specific permission, it’s important that you update your app to target API 23, and test the app thoroughly with Android Marshmallow users.

How to Get the Update

The Android emulator system images and developer preview system images have been updated for supported Nexus devices (Nexus 5, Nexus 6, Nexus 9 & Nexus Player) to help with your testing. You can download the device system images from the developer preview site. Also, similar to the previous developer update, supported Nexus devices will receive an Over-the-Air (OTA) update over the next couple days.
Although the Android 6.0 SDK is final, the devices system images are still developer preview versions. The preview images are near final but they are not intended for consumer use. Remember that when Android 6.0 Marshmallow launches to the public later this fall, you'll need to manually re-flash your device to a factory image to continue to receive consumer OTA updates for your Nexus device.

What is New

Compared to the previous developer preview update, you will find this final API update fairly incremental. You can check out all the API differences here, but a few of the changes since the last developer update include:
  • Android Platform Change:
    • Final Permissions User Interface — we updated the permissions user interface and enhanced some of the permissions behavior.
  • API Change:
    • Updates to the Fingerprint API — which enables better error reporting, better fingerprint enrollment experience, plus enumeration support for greater reliability.

Upload your Android Marshmallow apps to Google Play

Google Play is now ready to accept your API 23 apps via the Google Play Developer Console on all release channels (Alpha, Beta & Production). At the consumer launch this fall, the Google Play store will also be updated so that the app install and update process supports the new permissions model for apps using API 23.
To make sure that your updated app runs well on Android Marshmallow and older versions, we recommend that you use Google Play’s newly improved beta testing feature to get early feedback, then do a staged rollout as you release the new version to all users.

We finally have the gooey answer to the Android M conundrum and it’s Marshmallow. Not a major shock, it was always a front-runner, but some people have been surprised by the fact that Marshmallow will be version 6.0 of Android and not 5.2 or 5.5. Should a whole number leap imply some major overhaul? Why is Google jumping straight to 6.0? There are various possible reasons.

It never made sense

Did Google’s version system ever really make sense? Anyone who has worked with programmers will understand the often arbitrary nature of version numbers. Traditionally, the first number is supposed to mark a major version and the second number a minor version, but that’s just a general convention, it’s not an unbreakable rule. In practice, version numbers often just mark the point that something was pushed out the door. They’re useful because they make it possible to track down problems later, but they don’t really tell the end user anything, and they’re not really meant to.
Let’s take a brief look at the historical line-up of Android versions:
  • Android 1.0
  • Android 1.1
  • Android 1.5 Cupcake
  • Android 1.6 Donut
  • Android 2.0 Éclair
  • Android 2.2 Froyo
  • Android 2.3 Gingerbread
  • Android 3.0 Honeycomb
  • Android 4.0 Ice Cream Sandwich
  • Android 4.1 (4.2, 4.3) Jelly Bean
  • Android 4.4 Kitkat
  • Android 5.0 Lollipop
Take a look through the versions and try to find a pattern that establishes consistently why some versions are whole number leaps and others aren’t. The closest you could argue is probably that whole numbers indicate an aesthetic leap, but Éclair didn’t really and Marshmallow won’t either. What does it matter when the system never really made sense anyway?
The dessert names are for users, marking larger leaps of style and function, but even the incremental updates within names have sometimes delivered more than just bug fixes. There’s no real consistency there.

Responsive Full Width Ad

Copyright © 2016 Hostrings, powered by Blogger.