Review Results and Identify device and/or build specific issues

ASSIGNED
Assigned to

Status

ASSIGNED
4 years ago
4 years ago

People

(Reporter: relaas, Assigned: mellis)

Tracking

Details

(URL)

(Reporter)

Description

4 years ago
Review app testing results in the attached document and identify device and/or build specific issues. Once complete we will formulate a plan to address including a potential cause and recommended resolution path forward.

Example of issue: Identified app issue is NOT reproducible on Reference hardware running 1.3

Example Resolution path #1 - Notify FFOS Partner of the suspected device and/or build specific issues and request a fix for production hardware.
(Assignee)

Comment 1

4 years ago
Re: Twitter - Unable to reproduce this issue on reference hardware.  App launch and sign in to Twitter test account was successful across multiple devices. Is this issue still occurring on your end?
Flags: needinfo?(joseenrique.alvarezfernandez)
(Assignee)

Comment 2

4 years ago
re: Steel Story - Unable to reproduce this issue.  I was able to locate and download the "Steel Story" app from MP.  Listing in MP shows app is published and live in most locals including Mex, Col, US, UK, Brazil, Spain, Col, Venez, Poland, Peru, Uruguay, Argentina, Chile, El Salvador, Guatemala, Ecuador, Costa Rica, Panama, Nicaragua, & others.  

Is this issue still occurring on your end?
Hi all

As Twitter is finishing recoding their web backend and are not going to solve any bugs, I agreed with them to wait until their web backend is finished (ETA: mid december) and then retest their app and send to them all the bugs we've found
Flags: needinfo?(joseenrique.alvarezfernandez)
(Assignee)

Comment 4

4 years ago
@José - See "Steel Story" comment above.  Is this app still not discoverable when you search in Marketplace?
Flags: needinfo?(joseenrique.alvarezfernandez)
Nop. It is discoverable. Found it and installed it.
Flags: needinfo?(joseenrique.alvarezfernandez)
(Assignee)

Comment 6

4 years ago
Re: tvQu Online - App was rejected from MP on Oct 25th.  Will ping app review team for more information on this issue.
(Assignee)

Comment 7

4 years ago
Re Wassap: Wassap (471824) was deleted from MP after a report of Intellectual Property Infringement was received by the App Review Team.
(Assignee)

Updated

4 years ago
Depends on: 1107653
(Assignee)

Comment 8

4 years ago
@José - Would you mind taking a look at Jolicloud and confirming whether or not the screen is now fully-revealed in landscape mode. Also, please let me know if scrolling is now working well for you.
Flags: needinfo?(joseenrique.alvarezfernandez)
Hi there

Downloaded and tested on FIRE E and works fine to me.
Flags: needinfo?(joseenrique.alvarezfernandez)
(Assignee)

Comment 10

4 years ago
Re: MessageME: Service shut down, app was subsequently removed from Marketplace by app review lead.
(Assignee)

Comment 11

4 years ago
RE: PIANO - I am unable to replicate this issue.  App works well for me, with bass sounds on the left-hand side, where they needed to be. 

Would you mind confirming this issue is still occurring on your end, José?
Flags: needinfo?(joseenrique.alvarezfernandez)
Michael, on landscape mode the bass notes are on the left side of the piano (as it should) but put the app in portrait. Then you have the bass notes on the top keys.

Besides, if you play around flipping the device in landscape and portrait mode, you'll see that some keys do not appear. 

I've tested on OPEN C with v1.3 and FIRE E v2.0 and it happens on both
Flags: needinfo?(joseenrique.alvarezfernandez)
(Assignee)

Comment 13

4 years ago
Confirmed on Flame 1.3 & 2.0

José,  thanks for clarifying this, you are correct.  Bass notes appear at the top of the keyboard when app is in portrait mode.


Re: disappearing keys - from the screenshots of the app in MP, it appears as though there should be 14 keys total (8 white keys + 6 [really more like 5.75] black keys).  Switching from landscape to portrait, the only issue i notice is not actually "a disappearing of keys", but rather a change in the spacing between the white keys.  This leaves additional, unused real estate when the app is in landscape mode, making it appear as tho a key has disappeared.  Filing a bug on this now.
You need to log in before you can comment on or make changes to this bug.