Chromecast CAF - Automatic Reconnection management
I'm developing both an iOS and Android sender app, and after migrating from Cast SDK v2 to the Cast Application Framework (CAF) I'm no longer able to handle myself the connection to an already running receiver app.
My desired UX here is to prevent auto reconnections when user kills the app and runs it again, the user must explicitly connect again. It seems to me that the Automatic Reconnection feature is kicking on no matter what. On iOS nothing seems to be available, but on Android even setting the proper values seems to have no effect at all.
Are we now forced to use this UX or there is a solution for this? I didn't find anything on the UX guidelines forcing this behaviour.
Thanks
android ios google-cast asked Nov 20 '18 at 11:00
onibasonibas
1
add a comment |
I'm developing both an iOS and Android sender app, and after migrating from Cast SDK v2 to the Cast Application Framework (CAF) I'm no longer able to handle myself the connection to an already running receiver app.
My desired UX here is to prevent auto reconnections when user kills the app and runs it again, the user must explicitly connect again. It seems to me that the Automatic Reconnection feature is kicking on no matter what. On iOS nothing seems to be available, but on Android even setting the proper values seems to have no effect at all.
Are we now forced to use this UX or there is a solution for this? I didn't find anything on the UX guidelines forcing this behaviour.
Thanks
android ios google-cast asked Nov 20 '18 at 11:00
onibasonibas
1
add a comment |
I'm developing both an iOS and Android sender app, and after migrating from Cast SDK v2 to the Cast Application Framework (CAF) I'm no longer able to handle myself the connection to an already running receiver app.
My desired UX here is to prevent auto reconnections when user kills the app and runs it again, the user must explicitly connect again. It seems to me that the Automatic Reconnection feature is kicking on no matter what. On iOS nothing seems to be available, but on Android even setting the proper values seems to have no effect at all.
Are we now forced to use this UX or there is a solution for this? I didn't find anything on the UX guidelines forcing this behaviour.
Thanks
android ios google-cast asked Nov 20 '18 at 11:00
onibasonibas
1
I'm developing both an iOS and Android sender app, and after migrating from Cast SDK v2 to the Cast Application Framework (CAF) I'm no longer able to handle myself the connection to an already running receiver app.
My desired UX here is to prevent auto reconnections when user kills the app and runs it again, the user must explicitly connect again. It seems to me that the Automatic Reconnection feature is kicking on no matter what. On iOS nothing seems to be available, but on Android even setting the proper values seems to have no effect at all.
Are we now forced to use this UX or there is a solution for this? I didn't find anything on the UX guidelines forcing this behaviour.
Thanks
android ios google-cast android ios google-cast asked Nov 20 '18 at 11:00
onibasonibas
1
asked Nov 20 '18 at 11:00
onibasonibas
1
asked Nov 20 '18 at 11:00
onibasonibas
1
asked Nov 20 '18 at 11:00
onibasonibas
1
asked Nov 20 '18 at 11:00
onibasonibas
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There's a documentation about how to Migrate CCL Sender App to the Cast Application Framework (CAF).
All of the functionality of CCL has been implemented in CAF, so once you migrate, you will no longer need to use CCL.
If you're building a CAF sender app or migrating to CAF, you should be
using CastContext and not GoogleAPIClient for accessing the Cast API.
It is proper to use GoogleAPIClient for accessing other Google Play
services APIs.
For more info about the Reconnection Logic using CAF, read the documentation here.
answered Nov 21 '18 at 9:59
jessjess
1,078110
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%2f53391537%2fchromecast-caf-automatic-reconnection-management%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
There's a documentation about how to Migrate CCL Sender App to the Cast Application Framework (CAF).
All of the functionality of CCL has been implemented in CAF, so once you migrate, you will no longer need to use CCL.
If you're building a CAF sender app or migrating to CAF, you should be
using CastContext and not GoogleAPIClient for accessing the Cast API.
It is proper to use GoogleAPIClient for accessing other Google Play
services APIs.
For more info about the Reconnection Logic using CAF, read the documentation here.
answered Nov 21 '18 at 9:59
jessjess
1,078110
add a comment |
There's a documentation about how to Migrate CCL Sender App to the Cast Application Framework (CAF).
All of the functionality of CCL has been implemented in CAF, so once you migrate, you will no longer need to use CCL.
If you're building a CAF sender app or migrating to CAF, you should be
using CastContext and not GoogleAPIClient for accessing the Cast API.
It is proper to use GoogleAPIClient for accessing other Google Play
services APIs.
For more info about the Reconnection Logic using CAF, read the documentation here.
answered Nov 21 '18 at 9:59
jessjess
1,078110
add a comment |
There's a documentation about how to Migrate CCL Sender App to the Cast Application Framework (CAF).
All of the functionality of CCL has been implemented in CAF, so once you migrate, you will no longer need to use CCL.
If you're building a CAF sender app or migrating to CAF, you should be
using CastContext and not GoogleAPIClient for accessing the Cast API.
It is proper to use GoogleAPIClient for accessing other Google Play
services APIs.
For more info about the Reconnection Logic using CAF, read the documentation here.
answered Nov 21 '18 at 9:59
jessjess
1,078110
There's a documentation about how to Migrate CCL Sender App to the Cast Application Framework (CAF).
All of the functionality of CCL has been implemented in CAF, so once you migrate, you will no longer need to use CCL.
If you're building a CAF sender app or migrating to CAF, you should be
using CastContext and not GoogleAPIClient for accessing the Cast API.
It is proper to use GoogleAPIClient for accessing other Google Play
services APIs.
For more info about the Reconnection Logic using CAF, read the documentation here.
answered Nov 21 '18 at 9:59
jessjess
1,078110
answered Nov 21 '18 at 9:59
jessjess
1,078110
answered Nov 21 '18 at 9:59
jessjess
1,078110
answered Nov 21 '18 at 9:59
jessjess
1,078110
1,078110
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.
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%2f53391537%2fchromecast-caf-automatic-reconnection-management%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
