1145614 - Update fails for Hubii app

Status: RESOLVED DUPLICATE of bug 1148386

(Marketplace Graveyard :: Developer Pages, defect, P4)

Description

[Lisa Brewster [:adora]]

From Jose:

"I’ve been testing with a build version for the FIRE 2 for Uruguay and Peru and at the start of the device everything is right. I’ve received an update notification for some apps including Hubii. After accepting to update all the apps, everything went smooth except Hubii.

The version that was installed disappears and a red icon with an arrow appears. If I tap on it, it asks for a retry to download but a message appears that cannot be installed."

https://marketplace.firefox.com/app/hubii/

App history:
https://marketplace.firefox.com/reviewers/apps/review/hubii

Comment 1

[Michael Ellis]

Attachment: Hubii on Device.png

Comment 2

[Michael Ellis]

Attachment: Hubii First Launch.png

Comment 3

[Michael Ellis]

Tested this by Downloading Hubii from MP to Flame running 2.0.
At first glance, everything seems fine and as-it-should-be.
Attaching a screenshot of the app as it appears at first launch, as well as the app on the Device homescreen

@Jose- Can you provide a screenshot of your experience?

Comment 4

[joseenrique.alvarezfernandez]

Hi all

Testing on Woodduck with version 2.0 from scracth.
First, it appears the app and it works fine. I presume the app version 0.9.2.
I receive the notification of an update available (I presume version 0.9.3) and tap on it.
It seems it starts downloading but it's not able to install it. A red icon with an arrow appears. If you tap on it a message appears saying that there was an error while downloading the updates.

See all the screenshots attached.

The info about the device is:
Device: Woodduck
Version: 2.0.0.0

Comment 5

[joseenrique.alvarezfernandez]

Attachment: Hubii appears before update notification.png

Comment 6

[joseenrique.alvarezfernandez]

Attachment: Update notification.png

Comment 7

[joseenrique.alvarezfernandez]

Attachment: After trying update.png

Comment 8

[joseenrique.alvarezfernandez]

Attachment: Message that appears after tapping on red icon

Comment 10

[joseenrique.alvarezfernandez]

It seems that the problem is not Bug 1145160 as the issue is still happening

I've reset my device (WoodDuck with 2.0)and tried again but was not able to update Hubii.

I've look on Settings>Downloads and nothing was there. I still have 53 MB of storage on my device

So, I've deleted the app (now a red icon with an arrow) went to the marketplace and installed last version and it works just fine

So, in short, the problem is that I received a notification with some app updates and all of them work perfectly BUT Hubii.

Going to contact with developer but, could you please take a look at this issue?

Comment 11

[Beatriz Rodríguez [:brg]]

I have added in CC people from OEM so they can check if something is wrong in their side.

Comment 12

[Michael Ellis]

Bug 1145160 has been fixed and should have been push out yesterday, March 24th.

"This bug has been FIXED, but the fix has not been deployed to production yet. It will be on Tuesday 24 (see Target Milestone field) around 12:00 PST.

No further action from developers should be necessary."

@Jose - Can you check to see if the update has resolved the Hubii app issue for you?

Comment 13

[joseenrique.alvarezfernandez]

Hi Michael

Unfortunately, no

As Beatriz said the OEM are investigating as well as the developer

Comment 14

[jacobo.toll]

Dear all, any updates on the status of this bug?

Comment 15

[Michael Ellis]

I am unable to reproduce this issue, so it is difficult for me to test.

@ Jose - please let us know if this issue resolves on your end.

Comment 16

[Wil Clouser [:clouserw]]

bug 1148386 says "hubii updates perfectly" - I'm not sure if the context is the same but I'll close this since we haven't heard back in the last two comments.

Comment 17

[joseenrique.alvarezfernandez]

Hi guys

Will, there are two different bugs opened because the issue is affecting two different apps: Latch and Hubii. In this bug, the one affected is Hubii and in bug 1148386 the one affected is Latch but the context of both bugs seems to be the same.

I'm reopening this bug as this issue is not solved as it is still happening and it is easily reproducible by following (I'm testing with Woodduck with v2.0)
1. Start the device for the first time (make a factory reset if necessary)and connect it to Wifi/3G
2. Check that Hubii app is placed correctly and working fine (it is).Wait for the update notification
3. I received a message of 5 updates available: Hubii,  Line, Latch, Marketplace and Pinterest
4. Tap on Download
5. Downloading starts
6. All apps update adequately BUT Hubii. A message appears "There was an error while downloading the updates"
7. Hubii app is not updated as a red icon with an arrow appears where the app was.
8. By tapping on that red icon, a message asking if you want to download the app appears. If you tap on download it seems to start downloading until a message "There was an error while downloading the updates"

The process explained before is what happens to Latch in bug 1148386. This bug should not be closed until it is solved as it is also reproducible.

We really need some information about these two bugs as this is a serious issue that it's blocking us.

If you need more information, please ask.

Comment 18

[Wil Clouser [:clouserw]]

In comment 4 you say you presume the version of the app on device is 0.9.2 - can you verify that's the case?

Can you tell me what URL you are hitting to get the update and what the request/response looks like?

Is there a way I can test this?  Is the build you are trying in github somewhere?

Michael: it looks like you already did some digging on this, so maybe I'm behind the times with the questions above.  It sounds like this works fine on stock 2.0?  Any ideas?

Lisa - this bug is assigned to you.  Are you doing anything with it?

Comment 19

[Wil Clouser [:clouserw]]

It looks like Mathieu has requested more logs in bug 1145614.  Enabling those same preferences and attaching here would be good in addition to the questions in comment 18.  Thanks.

Comment 20

[Carmen Jimenez Cabezas]

I wouldn't like to add noise to the discussion, but I think that there is a situation that could produce this error.

If the app already installed has an origin (or doesn't have an origin set) and the update tries to set a different origin in the manifest, then the app update will fail as described. 

Lingling, could you verified if this is the situation (or not)? (i.e. the installed origin and the update origin are the same) please

Comment 21

[Miguel]

Dear Carmen,

I'm the Hubii App Developer. The origin, from our side, hasn't been changed from the start of the development.

  "origin": "app://hubii.com",

Anyway, I can't confirm if the origin is modified somehow during the preinstallation.

Regards!

Comment 22

[Mathieu Pillard [:mat]]

AFAIK when an app is to be preloaded, the app manifest url, origin and app *install* origin (as well as etag and package etag) need to be set in a file to make updates work. I don't have access to the builds so I can't verify those, sadly. That's why having logs as I requested in bug 1145614 is crucial to understand what's going on.

Comment 23

[David Palomino [:dpalomino]]

Dear Ling Ling, 

Do you have any feedback about this question from Carmen: 
---
I wouldn't like to add noise to the discussion, but I think that there is a situation that could produce this error.

If the app already installed has an origin (or doesn't have an origin set) and the update tries to set a different origin in the manifest, then the app update will fail as described. 

Lingling, could you verified if this is the situation (or not)? (i.e. the installed origin and the update origin are the same) please
---

thanks!
David

Comment 24

[jacobo.toll]

(In reply to David Palomino [:dpalomino] from comment #23)
> Dear Ling Ling, 
> 
> Do you have any feedback about this question from Carmen: 
> ---
> I wouldn't like to add noise to the discussion, but I think that there is a
> situation that could produce this error.
> 
> If the app already installed has an origin (or doesn't have an origin set)
> and the update tries to set a different origin in the manifest, then the app
> update will fail as described. 
> 
> Lingling, could you verified if this is the situation (or not)? (i.e. the
> installed origin and the update origin are the same) please
> ---
> 
> thanks!
> David

Hi David,

Speaking to Miguel, our team member who has developed the app, it seems like the origin is the same.

We, at Hubii, are running out of ideas in terms of what might be causing this error therefore if any of the other people on this thread can chip in it would be greatly appreciated.

Thanks to you all.

Jacobo.

Comment 25

[Mathieu Pillard [:mat]]

To re-iterate in a single comment what has been said elsewhere:

What would move this bug and bug 1148386 forward is either:
a) access to full logs (see https://bugzilla.mozilla.org/show_bug.cgi?id=1148386#c3 ) from people that can reproduce this bug

and/or

b) the code to the gaia build used by the same people.

Comment 26

[joseenrique.alvarezfernandez]

Hi guys

As I can't root the device (Woodduck) in which I can reproduce the error I've been looking at the app that failed specifically the manifest file which is the one that I understand could be the reason of this failure.

Attached to this bug there's a screenshot that compares the manifest file from Hubii version 0.9.2 (right side of the attached file) and Hubii version 0.9.4 (left side of the same attachment). As you may see there are 3 differences:
Line 3: changes the number version. This is totally reasonable
Line 11: The name changes from "Hubii" to "Hubii News". Don't think this could be the reason, but could you guys confirm?
Line 26: Name changes from "Hubii" to "Hubii Noticias". Same as above.

Besides this there isn't any other thing if you can't provide me a way to make the logcat on an non rooted device

Comment 27

[joseenrique.alvarezfernandez]

Attachment: Hubbi comparison.PNG

Comment 28

[Miguel]

Dear Jose Enrique,

the name of the app can't be the reason, because that's new from last version (0.9.4) and the error happened before (0.9.3) without that change... so it has to be another thing. :(

Comment 29

[jacobo.toll]

Dear all,

Is it possible to get a log output of the bug?

Comment 30

[Beatriz Rodríguez [:brg]]

We need OEM to unlock this situation. Please check and investigate the reason of the failure to make some progress.

Comment 31

[Lingling Zhao]

Hi All,

This bug is not the same with bug 1150442, bug 1150442 is caused by a special test patch which is not merged into the offical SW.

Actually I cannot reproduce this issue in my side, so I am unable to provide the useful log.

@[e-mail],
Do you do some special operation before the reproducing steps? 
In comment 17, the context of both bugs(this bug and bug 1148386)seems to be the same, but they donot happen in the same device? It seems that you cannot reproduce Hubii bug in SORA and Latch bug in Woodduck.

Comment 32

[joseenrique.alvarezfernandez]

Hi Lingling

No, I don't make any special operation before. 

Start the device from scratch (first time), wait for the update notification and install the updates. I did the same on both devices: Woodduck and Sora.

As explained, in Woodduck the app that fails is Hubii and in Sora is Latch but ins Sora Hubii updates with no problem and in Woodduck, Latch updates with no problem either

I've also tried, always starting the device as it will come from factory, to only install Hubii and Latch and not the other updates but the issue still happens.

Comment 33

[Beatriz Rodríguez [:brg]]

Lingling Zhao, you just need to wait till Hubii update from Marketplace is offered in Fire 2 build with customization(Hubii is preinstalled) and install the update. If you had any issue, please ping me or send mail.

Comment 34

[Lingling Zhao]

I have reproduced the latch bug and provide the useful logs in bug 1148386.
For this Hubii bug, I doesnot have the right SW for the Woodduck device at present, and will give the result ASAP.

Comment 35

[Mathieu Pillard [:mat]]

Marking as duplicate of bug 1148386 because without any additional information available it really looks like the same issue. The fix is to make sure the etag corresponding to the manifest for the preloaded apps is set to the correct value.

Comment 36

[Lingling Zhao]

Hi Beatriz,

I got a Wookduck device and its SW build, but the version for Hubbi is lower than 0.9.2, so I cannot reproduce this issue.

Do you have the package of 0.9.2?(Including application.zip, metadata.json and update.webapp)
Because latch issue is not reproduced on Wookduck, maybe they are different issues, we need logs to do more analysis.

Thanks.

Comment 37

[joseenrique.alvarezfernandez]

Hi all

I don't have the files (application.zip, metadata.json and update.webapp) for version 0.9.2 although I do have the application.zip for version 0.9.2 but not the metadata.json and updated.webapp

What I do have is the 3 files for version 0.5.1 (see attached file hubii.zip) that I believe will be useful to test as it is a previous version of the last app version published (which is 0.9.3). I don't really get why you need version 0.9.2 as , as far I understand, you will receive the update notification if you have a previous version of the last one sumitted

Comment 38

[joseenrique.alvarezfernandez]

Attachment: hubii.zip

Comment 39

[Lingling Zhao]

Using 0.5.1 in the attachment, I receive the notification of an update available and can update successfully.

I want version 0.9.2 because I see you presumed the app version 0.9.2 before update in Comment 4.
I need to test it according the steps of yours strictly, so can you please confirm what the version before update in your test?

Thanks.

Comment 40

[joseenrique.alvarezfernandez]

Hi LingLing

Attached is version 0.9.2. I don't have the metadata.json nor the update.webapp files. Sorry

As I don't have a rooted device I don't know which version was included in the build that was failing but I presume that you may be able to know it. Maybe any of your colleagues could help you here. Once you know, could you please let us know the Hubii version that is included in the build?

Just to clarify comment 4, I was assuming, although I wasn't sure, that the Hubii version that was included in the build was a previous version of the last one published on the marketplace. That doesn't mean that I was saying that the fail happens with version 0.9.2 as, I explained above, I couldn't know which Hubii version was preloaded in the build. Nevertheless, let's try with version 0.9.2

Comment 41

[joseenrique.alvarezfernandez]

Attachment: hubii-0.9.2.zip

Here is Hubii version 0.9.2

Comment 42

[joseenrique.alvarezfernandez]

Attachment: hubii-0.9.3.zip

Just in case, you needed here is version 0.9.3

The last version published on the Marketplace is 0.9.4 but I will not submit it here to avoid confussion and to be able to receive the notification update on the device

Comment 43

[Beatriz Rodríguez [:brg]]

Hi Lingling,
For your reference, the name of the failing build that I got is: Pixi3_3.5_FF_PE_v01.exe, it has operator customization, so I guess it was made by your local team in latam region. I hope it helps.
BR.
Beatriz.

Comment 44

[Lingling Zhao]

Cannot confirm what the internal build for Pixi3_3.5_FF_PE_v01.exe, so we send an email to CTS, and waiting for the response.

Comment 45

[David Palomino [:dpalomino]]

Dear Ling Ling, 

Do we have any update on this?

Thanks, 
David

Comment 46

[Lingling Zhao]

Still no response from CTS, I have sent another email again.

Comment 47

[joseenrique.alvarezfernandez]

Hi Lingling

Any update on this bug?

Comment 48

[Lingling Zhao]

Hi Dengwei,

Comment 49

[Lingling Zhao]

Hi DengWei,

Still no response from the CTS after my second email. This issue can not be reproduced in my side in Woodduck device, so please help to push the CTS give the useful information. 

Thanks.