Does Android debug keystore work with release keystore?
I have two Android apps that are designed to work together. One calls some interface method in the other. When they are released, they will use the same release keystore, so that they can talk to each other. But now my question is, if one of my app is still debugging using the debug keystore, and the other is using the release keystore, should the debugging app be able to talk to the release app? I was told that I can't do this before, but now I was told that I can. I asked my colleague and searched online but can't get an explanation. Can someone explain this? Thanks.
android android-keystore
add a comment |
I have two Android apps that are designed to work together. One calls some interface method in the other. When they are released, they will use the same release keystore, so that they can talk to each other. But now my question is, if one of my app is still debugging using the debug keystore, and the other is using the release keystore, should the debugging app be able to talk to the release app? I was told that I can't do this before, but now I was told that I can. I asked my colleague and searched online but can't get an explanation. Can someone explain this? Thanks.
android android-keystore
add a comment |
I have two Android apps that are designed to work together. One calls some interface method in the other. When they are released, they will use the same release keystore, so that they can talk to each other. But now my question is, if one of my app is still debugging using the debug keystore, and the other is using the release keystore, should the debugging app be able to talk to the release app? I was told that I can't do this before, but now I was told that I can. I asked my colleague and searched online but can't get an explanation. Can someone explain this? Thanks.
android android-keystore
I have two Android apps that are designed to work together. One calls some interface method in the other. When they are released, they will use the same release keystore, so that they can talk to each other. But now my question is, if one of my app is still debugging using the debug keystore, and the other is using the release keystore, should the debugging app be able to talk to the release app? I was told that I can't do this before, but now I was told that I can. I asked my colleague and searched online but can't get an explanation. Can someone explain this? Thanks.
android android-keystore
android android-keystore
asked Nov 12 '18 at 19:19
Runze
53
53
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
No, they don't. The debug keystore isn't anything special, its just a keystore that is automatically generated when you install Android Studio. If you have two apps that only work with the same signing key, then they will not work if one is release and one is debug.
But please note: depending on what you're doing, you don't need the same signing key to talk to each other. You only need it if you're doing very specific things, like broadcasting a signed permission.
Thanks @Gabe. That cleared things up for me. Our software product line does require the same signing key to work together. I double checked with the other team that makes the other software, and I was told even if it's called release version, it's currently signed with the debug keystore... /facepalm So both apps are debug. That's why they work together.
– Runze
Nov 12 '18 at 20:00
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',
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
);
);
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%2f53268725%2fdoes-android-debug-keystore-work-with-release-keystore%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
No, they don't. The debug keystore isn't anything special, its just a keystore that is automatically generated when you install Android Studio. If you have two apps that only work with the same signing key, then they will not work if one is release and one is debug.
But please note: depending on what you're doing, you don't need the same signing key to talk to each other. You only need it if you're doing very specific things, like broadcasting a signed permission.
Thanks @Gabe. That cleared things up for me. Our software product line does require the same signing key to work together. I double checked with the other team that makes the other software, and I was told even if it's called release version, it's currently signed with the debug keystore... /facepalm So both apps are debug. That's why they work together.
– Runze
Nov 12 '18 at 20:00
add a comment |
No, they don't. The debug keystore isn't anything special, its just a keystore that is automatically generated when you install Android Studio. If you have two apps that only work with the same signing key, then they will not work if one is release and one is debug.
But please note: depending on what you're doing, you don't need the same signing key to talk to each other. You only need it if you're doing very specific things, like broadcasting a signed permission.
Thanks @Gabe. That cleared things up for me. Our software product line does require the same signing key to work together. I double checked with the other team that makes the other software, and I was told even if it's called release version, it's currently signed with the debug keystore... /facepalm So both apps are debug. That's why they work together.
– Runze
Nov 12 '18 at 20:00
add a comment |
No, they don't. The debug keystore isn't anything special, its just a keystore that is automatically generated when you install Android Studio. If you have two apps that only work with the same signing key, then they will not work if one is release and one is debug.
But please note: depending on what you're doing, you don't need the same signing key to talk to each other. You only need it if you're doing very specific things, like broadcasting a signed permission.
No, they don't. The debug keystore isn't anything special, its just a keystore that is automatically generated when you install Android Studio. If you have two apps that only work with the same signing key, then they will not work if one is release and one is debug.
But please note: depending on what you're doing, you don't need the same signing key to talk to each other. You only need it if you're doing very specific things, like broadcasting a signed permission.
answered Nov 12 '18 at 19:22
Gabe Sechan
67.1k96297
67.1k96297
Thanks @Gabe. That cleared things up for me. Our software product line does require the same signing key to work together. I double checked with the other team that makes the other software, and I was told even if it's called release version, it's currently signed with the debug keystore... /facepalm So both apps are debug. That's why they work together.
– Runze
Nov 12 '18 at 20:00
add a comment |
Thanks @Gabe. That cleared things up for me. Our software product line does require the same signing key to work together. I double checked with the other team that makes the other software, and I was told even if it's called release version, it's currently signed with the debug keystore... /facepalm So both apps are debug. That's why they work together.
– Runze
Nov 12 '18 at 20:00
Thanks @Gabe. That cleared things up for me. Our software product line does require the same signing key to work together. I double checked with the other team that makes the other software, and I was told even if it's called release version, it's currently signed with the debug keystore... /facepalm So both apps are debug. That's why they work together.
– Runze
Nov 12 '18 at 20:00
Thanks @Gabe. That cleared things up for me. Our software product line does require the same signing key to work together. I double checked with the other team that makes the other software, and I was told even if it's called release version, it's currently signed with the debug keystore... /facepalm So both apps are debug. That's why they work together.
– Runze
Nov 12 '18 at 20:00
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%2f53268725%2fdoes-android-debug-keystore-work-with-release-keystore%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