View Issue Details

IDProjectCategoryView StatusLast Update
0011584MMASynchronizationpublic2013-12-22 04:42
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.0.4 
Target Version1.0.4Fixed in Version1.0.4 
Summary0011584: First time connection message is misleading / broken workflow & MMA won't terminate
DescriptionIf the user syncs a device to MMW that already has a profile for the MMA device, but the device itself has no sync info, then the following message briefly appears upon initiating the sync:

Choose where to sync your media fil...
--------------------------------------------
This is your first time
connecting to it, you will probably need to accept the
connection on the server in order to proceed.
[Cancel]

This is strange for several reasons:
a) If a connection has already been allowed, then the dialog appears very briefly--too briefly to read and then disappears. I would suggest that it should only appear if MMA has detected that MMW is blocking the connecting (e.g. after 2? seconds). That way the dialog will only appear if the connection is indeed being blocked in some way.

b) The Title doesn't match up to the message! The title should be something like 'Connecting...'

c) The message itself seems to be missing some text. It should be changed to:
Since this is your first time connecting to the server, you may need to accept the connection on the server in order to proceed.
[Cancel]

This is a minor issue, and is only labelled as urgent on the assumption that it is trivial to implement/low risk. Push to 1.0.5 if that's not the case.
TagsNo tags attached.
Attached Files
Fixed in build206

Relationships

has duplicate 0011632 closedLudek MMW v4 Disabling wifi sync in Device Profile results in many access requests 
related to 0013015 closedmarek MMA Multiple prompts to select storage location 

Activities

marek

2013-12-13 18:46

developer   ~0038765

I have fixed a) in build 201

But what kind of dialog you see ? I don't see cut text or title. Please see attached screenshot. What API/device do you use ?

rusty

2013-12-19 04:09

administrator   ~0038847

I can't replicate issue b). The only thing I can think of is that perhaps the dialog was somehow superimposed on the 'Choose where to sync your media files' dialog.

Re-assigning to Marek, since issue c) should be resolved as well.

marek

2013-12-19 23:59

developer   ~0038897

c) fixed in build 205

rusty

2013-12-20 05:51

administrator   ~0038900

Last edited: 2013-12-20 07:47

Tested 205 and there are several problems:

1 delete the Nexus5 profile in MMW
2 initiate a wi-fi sync
-->MMA appears to be stuck in the initialization phase--the reason being that MMW has popped up a dialog asking whether access should be granted, but MMA hasn't popped up its corresponding dialog. This issue seems to occur when the profile has been deleted from MMW, but not from MMA--if the profile/config info has been deleted from both, then the dialog appears as expected.



3 Press 'Cancel' in MMA
--> 'Everything is in sync' message appears even though synchronization never took place! Granted, nothing was selected, but the message implies that a sync occurred (even though it didn't / shouldn't have)!

--> MMA fails to terminate after the above scenario occurs. Even rebooting the device doesn't terminate the process--it must be force-terminated!

Note: I'm not sure which of these bugs are related to the change in the connection dialog--I can create separate bugs if necessary. Of these issues, the third is most critical since it may result in battery drain issues (and I wonder if it may be related to 0011458 ).

Ludek

2013-12-20 15:44

developer   ~0038912

Last edited: 2013-12-20 15:46

I can replicate and actually the same was reported by Lowlander as 0011632 yestarday.

As talked over Skype with Marek, it should be fixed on MMA side.

Test note: To reproduce you don't need to delete profile in MMW, you can just deselect [ ] Grant remote sync / access rights to ... checkbox

marek

2013-12-20 23:10

developer   ~0038925

Fixed in build 206

rusty

2013-12-22 04:42

administrator   ~0038956

Verified 206.