02-14-2012 01:36 PM - edited 02-14-2012 01:56 PM
This is the message I have received.
- navigation issue, cannot get back to home screen from options menu
But it is a standard android menu . Go back with player back key.
In the documentation, I can read this: Since the BlackBerry PlayBook tablet does not have a Back key, users must tap the Back button that appears at the bottom of the screen or use the Back gesture to display the previous screen. To use the Back gesture, users swipe from the bottom of the screen at a 45 degree angle toward the left side of the screen. Note: A navigation bar with a Back button appears at the bottom of most applications. For applications that use full screen mode (for example, games) users can swipe down from the top of the screen to display the navigation bar.
What have I to do?
Thanks a lot!
Solved! Go to Solution.
02-15-2012 01:20 PM
I got the same denial email today:
'functionality issue: cannot navigate to home menu from preferences'
Anyone plan on resubmitting their application with code that exits out of the menu back into the Activity or do we plan to fight this? I thought there was navigation as stated in the documentation so I didn't even think about this issue coming up.
Thanks in advance - hopefully we hear from someone about this.
02-15-2012 02:13 PM
I just got denied too:
- navigation issue: cannot navigate back to home menu
I tested all my apps and the button at the bottom left works. I navigated around as expected. Does anyone have an explanation of what they REALLY want? If I add a menu item to go back for each page would that work? Do I have to handle the swipe gesture that they mentioned?
Someone from RIM needs to clear up what the actual requirements are. I thought the intention was to get Android apps over pretty much as is. If I have to implement swipe gestures on every page that's going to be very close to a show stopper.
02-15-2012 02:36 PM
02-15-2012 03:12 PM
Wow, on this basis they would have to reject every Android app in existence surely? There's a big difference between repackaging an app for Playbook with some code redacted and actually porting it with major additions (my app is quite large with 20 preference screens and 31 options menus).
This must be a mistake?
02-16-2012 12:52 AM - edited 02-16-2012 12:53 AM
It sounds more like a miscommunication with the testing lab (perhaps some of the reviewers who are "working around the clock" haven't been properly briefed?)
I'm sure we would have been told if there was a requirement to have a non-standard exit button on an options menu or preference screen.