View Issue Details

IDProjectCategoryView StatusLast Update
0013211MMAUPnP / Castingpublic2016-06-28 23:42
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionfixed 
PlatformHuawei Y6OSAndroid 5.1 
Product Version1.2.0 
Target Version1.2.0Fixed in Version1.2.0 
Summary0013211: Failed casting doesn't generate any error message
DescriptionWhen testing with a Y6 device, it failed to connect to chromecast devices. This failure also occurred with other apps so it's probably not an MMA issue. However, rather than failing silently, MMA should generate some sort of error message. e.g.

Failed to connect to _Google Play Services_.

Try rebooting your Android device, your Google Cast device, and your router.

-----------
Are there other error conditions that we should document?

p.s. any ideas why this device might be having problems? Could it be related to the fact that I sideloaded this build of MMA?
Additional InformationDebug log:
KST5BLHNQH
TagsNo tags attached.
Fixed in build590

Activities

martin

2016-04-08 11:35

developer   ~0044413

Last edited: 2016-04-08 11:40

There is flag of disconnection reason. This flag can have values:
DISCONNECT_REASON_OTHER://unknown reason
 showToast(Connection failed!);
DISCONNECT_REASON_CONNECTIVITY://e.g weak wifi signal
 showToast(Connectivity lost);
DISCONNECT_REASON_APP_NOT_RUNNING://e.g another app takes control
 showToast(App was taken over or not available anymore); //dialog shows only when MMA is in foreground (maybe can happen on android N)1
DISCONNECT_REASON_EXPLICIT://Intentional disconnect - do nothing


I have added toast message for first three reasons, but the REASON_EXPLICIT is intentional disconnect e.g. when user disconnect via dialog(usual usecase). So I think that toast message is undesirable.
On other hand your disconnection reason is also EXPLICIT. I had similar issue with Nexus 7 after system update. No app wasn't able to cast. It took one day, then maybe I updated Google Play Services or restarted device and then it work as before. Strange.


Fixed in build 1.2.0.590

peke

2016-06-28 23:42

developer   ~0045066

Verified 607