Google Maps is not working properly after publishing an app in Google Play store












0














I developed an Android app which contains Map Activity. Before publishing the application and now the map works properly in the emulator, but the map in the app published in google play does not appear. there is no problem in the position of the device or in the locations where I search, also calculates the distance between the location of the device and the location where I search but the map is completely grayed out. How can I solve this problem?










share|improve this question
























  • problem is in the development key that you used for production build, as I think
    – Vladyslav Matviienko
    Nov 21 '18 at 10:51










  • Did you generate SignAPK for publish? and Have you used SHA1 key anywhere??
    – Harshil kakadiya
    Nov 21 '18 at 11:19












  • i signed my APK before release. i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app.
    – Kemal Aydeniz
    Nov 21 '18 at 11:45
















0














I developed an Android app which contains Map Activity. Before publishing the application and now the map works properly in the emulator, but the map in the app published in google play does not appear. there is no problem in the position of the device or in the locations where I search, also calculates the distance between the location of the device and the location where I search but the map is completely grayed out. How can I solve this problem?










share|improve this question
























  • problem is in the development key that you used for production build, as I think
    – Vladyslav Matviienko
    Nov 21 '18 at 10:51










  • Did you generate SignAPK for publish? and Have you used SHA1 key anywhere??
    – Harshil kakadiya
    Nov 21 '18 at 11:19












  • i signed my APK before release. i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app.
    – Kemal Aydeniz
    Nov 21 '18 at 11:45














0












0








0







I developed an Android app which contains Map Activity. Before publishing the application and now the map works properly in the emulator, but the map in the app published in google play does not appear. there is no problem in the position of the device or in the locations where I search, also calculates the distance between the location of the device and the location where I search but the map is completely grayed out. How can I solve this problem?










share|improve this question















I developed an Android app which contains Map Activity. Before publishing the application and now the map works properly in the emulator, but the map in the app published in google play does not appear. there is no problem in the position of the device or in the locations where I search, also calculates the distance between the location of the device and the location where I search but the map is completely grayed out. How can I solve this problem?







android google-maps google-play






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 21 '18 at 10:45









Fantômas

32.3k156388




32.3k156388










asked Nov 21 '18 at 10:31









Kemal Aydeniz

227




227












  • problem is in the development key that you used for production build, as I think
    – Vladyslav Matviienko
    Nov 21 '18 at 10:51










  • Did you generate SignAPK for publish? and Have you used SHA1 key anywhere??
    – Harshil kakadiya
    Nov 21 '18 at 11:19












  • i signed my APK before release. i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app.
    – Kemal Aydeniz
    Nov 21 '18 at 11:45


















  • problem is in the development key that you used for production build, as I think
    – Vladyslav Matviienko
    Nov 21 '18 at 10:51










  • Did you generate SignAPK for publish? and Have you used SHA1 key anywhere??
    – Harshil kakadiya
    Nov 21 '18 at 11:19












  • i signed my APK before release. i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app.
    – Kemal Aydeniz
    Nov 21 '18 at 11:45
















problem is in the development key that you used for production build, as I think
– Vladyslav Matviienko
Nov 21 '18 at 10:51




problem is in the development key that you used for production build, as I think
– Vladyslav Matviienko
Nov 21 '18 at 10:51












Did you generate SignAPK for publish? and Have you used SHA1 key anywhere??
– Harshil kakadiya
Nov 21 '18 at 11:19






Did you generate SignAPK for publish? and Have you used SHA1 key anywhere??
– Harshil kakadiya
Nov 21 '18 at 11:19














i signed my APK before release. i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app.
– Kemal Aydeniz
Nov 21 '18 at 11:45




i signed my APK before release. i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app.
– Kemal Aydeniz
Nov 21 '18 at 11:45












1 Answer
1






active

oldest

votes


















0














Seems like your API key for google maps is restricted.




For Android apps, you restrict the key to your app's package name and SHA-1 signing-certificate fingerprint.




You can see key restrictions in Google developer console
Check the package name of local builds and published one. Then SHA1 of release and debug certificate. You can download release apk from Google Play console and get SHA1 of cert as described here.






share|improve this answer





















  • i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app. Do you mean change to none restriction?
    – Kemal Aydeniz
    Nov 21 '18 at 11:43










  • No, please check your restrictions. Compare packageName of release app and SHA1 from key restrictions with real values from published apk. I've been in same situation. I just made a typo in package name.
    – nnesterov
    Nov 21 '18 at 13:02











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53410111%2fgoogle-maps-is-not-working-properly-after-publishing-an-app-in-google-play-store%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Seems like your API key for google maps is restricted.




For Android apps, you restrict the key to your app's package name and SHA-1 signing-certificate fingerprint.




You can see key restrictions in Google developer console
Check the package name of local builds and published one. Then SHA1 of release and debug certificate. You can download release apk from Google Play console and get SHA1 of cert as described here.






share|improve this answer





















  • i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app. Do you mean change to none restriction?
    – Kemal Aydeniz
    Nov 21 '18 at 11:43










  • No, please check your restrictions. Compare packageName of release app and SHA1 from key restrictions with real values from published apk. I've been in same situation. I just made a typo in package name.
    – nnesterov
    Nov 21 '18 at 13:02
















0














Seems like your API key for google maps is restricted.




For Android apps, you restrict the key to your app's package name and SHA-1 signing-certificate fingerprint.




You can see key restrictions in Google developer console
Check the package name of local builds and published one. Then SHA1 of release and debug certificate. You can download release apk from Google Play console and get SHA1 of cert as described here.






share|improve this answer





















  • i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app. Do you mean change to none restriction?
    – Kemal Aydeniz
    Nov 21 '18 at 11:43










  • No, please check your restrictions. Compare packageName of release app and SHA1 from key restrictions with real values from published apk. I've been in same situation. I just made a typo in package name.
    – nnesterov
    Nov 21 '18 at 13:02














0












0








0






Seems like your API key for google maps is restricted.




For Android apps, you restrict the key to your app's package name and SHA-1 signing-certificate fingerprint.




You can see key restrictions in Google developer console
Check the package name of local builds and published one. Then SHA1 of release and debug certificate. You can download release apk from Google Play console and get SHA1 of cert as described here.






share|improve this answer












Seems like your API key for google maps is restricted.




For Android apps, you restrict the key to your app's package name and SHA-1 signing-certificate fingerprint.




You can see key restrictions in Google developer console
Check the package name of local builds and published one. Then SHA1 of release and debug certificate. You can download release apk from Google Play console and get SHA1 of cert as described here.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 21 '18 at 10:54









nnesterov

867420




867420












  • i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app. Do you mean change to none restriction?
    – Kemal Aydeniz
    Nov 21 '18 at 11:43










  • No, please check your restrictions. Compare packageName of release app and SHA1 from key restrictions with real values from published apk. I've been in same situation. I just made a typo in package name.
    – nnesterov
    Nov 21 '18 at 13:02


















  • i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app. Do you mean change to none restriction?
    – Kemal Aydeniz
    Nov 21 '18 at 11:43










  • No, please check your restrictions. Compare packageName of release app and SHA1 from key restrictions with real values from published apk. I've been in same situation. I just made a typo in package name.
    – nnesterov
    Nov 21 '18 at 13:02
















i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app. Do you mean change to none restriction?
– Kemal Aydeniz
Nov 21 '18 at 11:43




i restricted app with package name and SHA-1 signing-certificate fingerprint on Google Developer Console before release app. Do you mean change to none restriction?
– Kemal Aydeniz
Nov 21 '18 at 11:43












No, please check your restrictions. Compare packageName of release app and SHA1 from key restrictions with real values from published apk. I've been in same situation. I just made a typo in package name.
– nnesterov
Nov 21 '18 at 13:02




No, please check your restrictions. Compare packageName of release app and SHA1 from key restrictions with real values from published apk. I've been in same situation. I just made a typo in package name.
– nnesterov
Nov 21 '18 at 13:02


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53410111%2fgoogle-maps-is-not-working-properly-after-publishing-an-app-in-google-play-store%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Wiesbaden

Marschland

Dieringhausen