Android Alpha Internal Release Cannot Log In. Where can I check the log files?
up vote
0
down vote
favorite
I've released my app in internal alpha on google play, received the URL, and installed the app on a phone via the URL link. There is a bug where users cannot log in. If the app is installed with android studio via USB link, the app works fine, even if I disconnect the USB from the PC running Android studio, the app works fine without the login issue. If the app is installed via the play store URL link, the bug occurs.
1.) What difference is there between Android Studio installing an app on a phone and Google Play (Internal Alpha) URL links installing an app on a phone? Specifically, what differences are there that would cause a login problem?
Because this bug doesn't happen when I use android studio to launch the app, I can't use Android Studio to view the logs while the app is running!
2.) What tools can I use to diagnose this problem on an independently running android device? (Galaxy S7 in this case). Perhaps there a way I can view the logs of the app on the phone? Or use Android Studio to view the debug of the running app without using Android Studio to install the app?
android 
android-studio 
google-play android-log asked Oct 23 at 17:22
Alan Nelson
3311317
add a comment |
up vote
0
down vote
favorite
I've released my app in internal alpha on google play, received the URL, and installed the app on a phone via the URL link. There is a bug where users cannot log in. If the app is installed with android studio via USB link, the app works fine, even if I disconnect the USB from the PC running Android studio, the app works fine without the login issue. If the app is installed via the play store URL link, the bug occurs.
1.) What difference is there between Android Studio installing an app on a phone and Google Play (Internal Alpha) URL links installing an app on a phone? Specifically, what differences are there that would cause a login problem?
Because this bug doesn't happen when I use android studio to launch the app, I can't use Android Studio to view the logs while the app is running!
2.) What tools can I use to diagnose this problem on an independently running android device? (Galaxy S7 in this case). Perhaps there a way I can view the logs of the app on the phone? Or use Android Studio to view the debug of the running app without using Android Studio to install the app?
android android-studio google-play android-log asked Oct 23 at 17:22
Alan Nelson
3311317
Have you generated signature apk for alpha release?
– K M Rejowan Ahmmed
Oct 23 at 17:30
Yes. I've generated a signed APK via Android Studio >> Build >> Generate Signed APK. I selected "Jar Signature" and "Full APK signature" options. I've also enabled "Google Play App Signing" via the developer console. Could that have something to do with it? Perhaps I should try re-uploading a new signed APK or using Google Play to download a new keystore file if I did something out of order?
– Alan Nelson
Oct 24 at 16:59
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've released my app in internal alpha on google play, received the URL, and installed the app on a phone via the URL link. There is a bug where users cannot log in. If the app is installed with android studio via USB link, the app works fine, even if I disconnect the USB from the PC running Android studio, the app works fine without the login issue. If the app is installed via the play store URL link, the bug occurs.
1.) What difference is there between Android Studio installing an app on a phone and Google Play (Internal Alpha) URL links installing an app on a phone? Specifically, what differences are there that would cause a login problem?
Because this bug doesn't happen when I use android studio to launch the app, I can't use Android Studio to view the logs while the app is running!
2.) What tools can I use to diagnose this problem on an independently running android device? (Galaxy S7 in this case). Perhaps there a way I can view the logs of the app on the phone? Or use Android Studio to view the debug of the running app without using Android Studio to install the app?
android android-studio google-play android-log asked Oct 23 at 17:22
Alan Nelson
3311317
I've released my app in internal alpha on google play, received the URL, and installed the app on a phone via the URL link. There is a bug where users cannot log in. If the app is installed with android studio via USB link, the app works fine, even if I disconnect the USB from the PC running Android studio, the app works fine without the login issue. If the app is installed via the play store URL link, the bug occurs.
1.) What difference is there between Android Studio installing an app on a phone and Google Play (Internal Alpha) URL links installing an app on a phone? Specifically, what differences are there that would cause a login problem?
Because this bug doesn't happen when I use android studio to launch the app, I can't use Android Studio to view the logs while the app is running!
2.) What tools can I use to diagnose this problem on an independently running android device? (Galaxy S7 in this case). Perhaps there a way I can view the logs of the app on the phone? Or use Android Studio to view the debug of the running app without using Android Studio to install the app?
android android-studio google-play android-log android android-studio google-play android-log asked Oct 23 at 17:22
Alan Nelson
3311317
asked Oct 23 at 17:22
Alan Nelson
3311317
asked Oct 23 at 17:22
Alan Nelson
3311317
asked Oct 23 at 17:22
Alan Nelson
3311317
asked Oct 23 at 17:22
Alan Nelson
3311317
3311317
Have you generated signature apk for alpha release?
– K M Rejowan Ahmmed
Oct 23 at 17:30
Yes. I've generated a signed APK via Android Studio >> Build >> Generate Signed APK. I selected "Jar Signature" and "Full APK signature" options. I've also enabled "Google Play App Signing" via the developer console. Could that have something to do with it? Perhaps I should try re-uploading a new signed APK or using Google Play to download a new keystore file if I did something out of order?
– Alan Nelson
Oct 24 at 16:59
add a comment |
Have you generated signature apk for alpha release?
– K M Rejowan Ahmmed
Oct 23 at 17:30
Yes. I've generated a signed APK via Android Studio >> Build >> Generate Signed APK. I selected "Jar Signature" and "Full APK signature" options. I've also enabled "Google Play App Signing" via the developer console. Could that have something to do with it? Perhaps I should try re-uploading a new signed APK or using Google Play to download a new keystore file if I did something out of order?
– Alan Nelson
Oct 24 at 16:59
Have you generated signature apk for alpha release?
– K M Rejowan Ahmmed
Oct 23 at 17:30
Have you generated signature apk for alpha release?
– K M Rejowan Ahmmed
Oct 23 at 17:30
Yes. I've generated a signed APK via Android Studio >> Build >> Generate Signed APK. I selected "Jar Signature" and "Full APK signature" options. I've also enabled "Google Play App Signing" via the developer console. Could that have something to do with it? Perhaps I should try re-uploading a new signed APK or using Google Play to download a new keystore file if I did something out of order?
– Alan Nelson
Oct 24 at 16:59
Yes. I've generated a signed APK via Android Studio >> Build >> Generate Signed APK. I selected "Jar Signature" and "Full APK signature" options. I've also enabled "Google Play App Signing" via the developer console. Could that have something to do with it? Perhaps I should try re-uploading a new signed APK or using Google Play to download a new keystore file if I did something out of order?
– Alan Nelson
Oct 24 at 16:59
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of
project overview] (top of the screen) >> Project Settings >> General
[Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:44
Alan Nelson
3311317
add a comment |
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',
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52954626%2fandroid-alpha-internal-release-cannot-log-in-where-can-i-check-the-log-files%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
up vote
0
down vote
accepted
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of
project overview] (top of the screen) >> Project Settings >> General
[Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:44
Alan Nelson
3311317
add a comment |
up vote
0
down vote
accepted
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of
project overview] (top of the screen) >> Project Settings >> General
[Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:44
Alan Nelson
3311317
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of
project overview] (top of the screen) >> Project Settings >> General
[Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:44
Alan Nelson
3311317
The problem was created when Google Play App Signing was enabled for my app. Google Play App Signing changes the SHA-1 certificate fingerprint (from what is in my keystore) to their own SHA-1 certificate fingerprint.
The fix:
Goto https://play.google.com/apps/publish/
Click your application >> Release Management >> App Signing.
You will see "App signing certificate" and "Upload certificate"
Copy the SHA-1 From "App Signing Certificate." (THE TOP ONE)
Goto https://console.firebase.google.com/
Click your application >> Settings [Gearbox Icon to the right of
project overview] (top of the screen) >> Project Settings >> General
[Tab] >> Add Fingerprint
Paste the SHA-1 App Signing Certificate. Save.
All fixed!
answered Nov 12 at 7:44
Alan Nelson
3311317
answered Nov 12 at 7:44
Alan Nelson
3311317
answered Nov 12 at 7:44
Alan Nelson
3311317
answered Nov 12 at 7:44
Alan Nelson
3311317
3311317
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52954626%2fandroid-alpha-internal-release-cannot-log-in-where-can-i-check-the-log-files%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Have you generated signature apk for alpha release?
– K M Rejowan Ahmmed
Oct 23 at 17:30
Yes. I've generated a signed APK via Android Studio >> Build >> Generate Signed APK. I selected "Jar Signature" and "Full APK signature" options. I've also enabled "Google Play App Signing" via the developer console. Could that have something to do with it? Perhaps I should try re-uploading a new signed APK or using Google Play to download a new keystore file if I did something out of order?
– Alan Nelson
Oct 24 at 16:59