configuration popup

[owncloud]

configuration popup

[davivel]

This is definitely a bug. You shouldn't see that popup when entering the app. Could you tell us what model is your device, and what version of Android it holds?

[przybylski]

This is not a bug, android 2.2 cannot execute account manager directly. This can be done from API 9. Thats why we are showing this popup

[rperezb]

On the other hand, I would like to know too which ownCloud version you are working with.

[davivel]

It's never shown directly, but it's "tricked". The FileDisplayActivity is triggered, but when no account is available, the AccountManager is immediately "called". It's working both in Android 2.2 emulator and in real 2.2 devices (Galaxy Mini).

The popup is there to be shown if the users click BACK or CANCEL in the login screen. If it's shown when the app is started, that's a bug.

Anyway, the flow for the first gave a lot of headaches in some devices. This is something to be reworked... again

[jancborchardt]

I have a Google G1 / HTC Dream with Android 2.2.1. The ownCloud version is the free one from owncube.com, ownCloud 4.0.8.

I didn’t click back or cancel in the log in screen I just filled in the details and clicked connect.

[davivel]

And then you saw the file list behind the popup. Well, then that's a bug. The popup should be automatically dismissed.

Great device to make hard tests. If we start to measure performance we can't choose any other more challenging :)

[jancborchardt]

On Wed, Nov 7, 2012 at 12:15 PM, David A. Velasco
[email protected]:

Great device to make hard tests. If we start to measure performance we
can't choose any other more challenging :)

Yeah, the joke is on me. ;)

[davivel]

Working on this.

[davivel]

Finished with this here: #158 .

@jancborchardt , @rperezb will review here. Meanwhile I will go on with UX fixes & improvements in setup screen. Maybe you prefer to wait we solve some more before having a look.

[rperezb]

Tested!
It has been tested on:

Galay tab( (3.2)
Emulator ( 4.1.2)
Tab ( 2.3.1)

From now, we consider this task as closed, in case someone detects it does not work, please, reopen it.