569103 - amo won't let android latest nightly build install sync client

Status: RESOLVED INVALID

(Firefox :: Sync, defect)

Description

[chris hofmann]

still a bit of confusion about how to get sync going on android nightlies

http://groups.google.com/group/fennec-android-pre-alpha  says:

  * 1.3 beta works, and can be installed by going to https://services.mozilla.com/sync/install.php

but that link redirects to amo.

clicking on the "install" button on amo from the 2010 05 29 build gets an amo version check mismatch.   says I have 2.0a1 pre and I need firefox 3.x

we should update the check to allow android/mobile user agents that are at 2.x to be accepted of the amo install if that xpi works with latest nightlies.

we should also update the page on the google group with something that works better.

Comment 1

[chris hofmann]

vlad's old blog post with the orginal weave set up instructions also now has an out of date path to inaccurate info.

http://blog.vlad1.com/2010/04/27/fennec-on-android-ground-zero/

points at https://mozillalabs.com/weave/ which now redirects to -> 

https://mozillalabs.com/sync/

but that page has old 1.2 stuff and references to weave.

Comment 2

[Mike Connor [:mconnor]]

https://services.mozilla.com/sync/install.php directs to the latest dev channel build, which as of now is 
https://ftp.mozilla.org/pub/mozilla.org/labs/weave/development/1.3.x/weave-1.3-dev.xpi which should work fine on Android (and people were installing it on Friday).

I don't have an Android phone, so I can't verify any of this right now, but if AMO is claiming you're on Firefox, they need to fix their version checks.  If the client is producing the error, maybe someone screwed up the app ID?

I don't think this is a Sync bug though.

Comment 3

[Matt Brubeck (:mbrubeck)]

Add-on installation is actually completely broken in the latest Android nightlies.  I've clarified https://wiki.mozilla.org/Mobile/Platforms/Android and updated the Google Groups page to note this.

This will be fixed when the Android patches finish landing on mozilla-central.  But the compatibility problem will remain.  The wiki page has a work-around for this.  We could provide a "nightly tester tools" add-on like the one for Firefox, to make the workaround easier.

We could also update AMO to include 2.0a1pre as an allowed Fennec version, but there is a downside to this: most current extensions - including Weave - are not actually compatible with all of our 2.0a1pre builds (such as the electrolysis builds that will probably become the Fennec 2.0a1 release).  We may want to wait until after Electrolysis lands before asking developers to test and mark extensions for 2.0 alpha compatibility.

(In reply to comment #1)
> https://mozillalabs.com/sync/
> but that page has old 1.2 stuff and references to weave.

The download link on that page is up to date; it's only the old blog entries that still refer to Weave.

Comment 4

[Matt Brubeck (:mbrubeck)]

(In reply to comment #3)
> The download link on that page is up to date; it's only the old blog entries
> that still refer to Weave.

Actually, I see some of the sidebar links on https://mozillalabs.com/sync/ still refer to Weave too.  (I think the Sync team is still transitioning their web pages...)

Comment 5

[chris hofmann]

I can't telll exactly what is going wrong when I try to hit
https://services.mozilla.com/sync/install.php

with the nightly android build but it doesn't result in the ability to install the addon.

I get progress indicator showing something is happening but then it appears a redirect back to https://services.mozilla.com/.   I try adding back the sync/install.php part of the path and get the same thing again.

I don't ever get an addon install window, and I don't get anything showing up in the download manager like I might see if the .xpi format wasn't recognized.

Comment 6

[Matt Brubeck (:mbrubeck)]

(In reply to comment #5)
> I don't ever get an addon install window, and I don't get anything showing up
> in the download manager like I might see if the .xpi format wasn't recognized.

This is because the new add-ons manager (bug 554007) hasn't landed on the mozilla-droid branch, which our Android nightlies use.  Add-ons do not work in current Android nightlies.  This will be fixed when Android is merged into trunk (currently about a half-dozen patches waiting on review before this can happen).

I also filed bug 569131 and bug 569132 about some links that go to the non-mobile AMO page instead of the mobile one.

Comment 7

[Mike Connor [:mconnor]]

As reported, this is invalid (it's primarily about the android bustage)  there's a different bug about the web stuff.