failed Windows Phone validation for 3 reasons

[cfullerNY]

#1

Requirements
A Windows Phone app is deactivated when the
user presses the Start button or if the device
timeout causes the lock screen to engage. A
Windows Phone app is also deactivated with it
invokes a Launcher or Chooser API.

A Windows Phone OS 7.0 app is tombstoned
(terminated) when it is deactivated. A Windows
Phone OS 7.1 or higher app becomes Dormant
when it is deactivated but can be terminated by
the system when resource use policy causes it to
tombstone.

When activated after termination, the app must meet the requirements in Section 5.2.1 - Launch
time.

Expected Result
Test Process Required
1. Launch your application.
2. Deactivate the application using the Start
button.
3. Launch your application again.
4. Verify that the application launches normally
within 5 seconds, and is responsive within 20
seconds of launching.
5. If your application includes pause
functionality, pause the application.
6. Launch your application again.
7. Verify that the application launches normally
within 5 seconds, and is responsive within 20
seconds of launching.

Comments: When the user deactivates the application, the application does not reactivate when the user presses the
device Back button immediately or after waiting for ten seconds.
Steps to Reproduce:
1. Launch the application.
2. Deactivate the application by pressing the Start button, Bing button, or Power button.
3. Press the device Back button immediately or after waiting for ten seconds to reactivate the application.
4. Observe the application does not respond to user input.

#2

Requirements
Pressing the Back button from the first screen of
an application must close the application.

Comments: Pressing the device back button has no effect on the application.
Steps to Reproduce:
1. Launch the application.
2. Press the device Back button.
3. Observe the application does not respond.
This occurs on every page of the application.
This is the first submission of the application.

#3

Requirements
For Windows Phone OS 7.0 and Windows Phone
OS 7.1
An app must not exceed 90 MB of RAM usage,
except on devices that have more than 256 MB of
memory.
You can use the DeviceExtendedProperties and
DeviceStatus classes to query the amount of
memory that your app is using, and to adjust
behavior based upon the memory available on the
device.
For more info on memory requirements for
Windows Phone, see App memory limits for
Windows Phone 8.

Comments: The application terminates unexpectedly on devices with 256-MB of memory.
Steps to reproduce:
1. Launch the application.
2. Tap "bounty list" button.
3. Observe the application unexpectedly terminates.
Only occurs on Windows Phone 7 devices with 256-MB of memory.

#1 I have no idea how I can deal with this. any Windows Phone experts have any advice?

#2 another phone physical button issue. basically the same as #1 from what I can tell

#3 is a memory management issue that I know how to fix: I'll completely remove this extra feature from the game. good work, Microsoft!

[colej_uk]

#1 and #2 is the problem identified here: http://community.clickteam.com/showthread.php?t=78727 we're waiting on a fix. Any progress on this Francois?

[cfullerNY]

more from a contact at nokia:

problem A - The back button did not work for me as well. I was actually unable to
quick/exit the game using the back button - this is required.

problem B - Look if there are any memory leaks or objects you can dispose of. Also, call
GC.Collect after loading resources or change scenes in the game to reclaim unused
memory.

[Francois]

Still waiting for my WP8 phone to arrive... Should be anytime now.

[cfullerNY]

Hi, has there been any update on this?

I'd like to reiterate that I purchased a Nokia Lumia 710 as well as the XNA exporter specifically to build a Windows Phone app with MMF2 and I AM NOT ABLE TO DO SO.

[cfullerNY]

if other people have apps on the windows phone store that don't have this freeze bug, is it possible for me to use this old version of the XNA exporter?

[Dobermann]

if other people have apps on the windows phone store that don't have this freeze bug, is it possible for me to use this old version of the XNA exporter?

I've released an update to my WP game using the last version of XNA and i have no problem.
I'm making a new game for WP with the last version of the XNA and it is working fine.

[cfullerNY]

what have you done to get around the bug '[Windows Phone] Freezing on game resume' ? aside from a memory leak (I can completely remove this feature if need be), this is the reason why I can't go live. my app works fine on the phone.

[Dobermann]

Simply make an app with the 7.0 SDK dude! The 7.1 SDK isn't supported by MMF2 XNA module because they didn't added the FAS function. But for now, just make 7.0 projects with Visual Studio and it will works fine ! On resume the game will restart, but that's not a big deal.

[cfullerNY]

Simply make an app with the 7.0 SDK dude! The 7.1 SDK isn't supported by MMF2 XNA module because they didn't added the FAS function. But for now, just make 7.0 projects with Visual Studio and it will works fine ! On resume the game will restart, but that's not a big deal.

will try this as soon as I get home, many thanks. where do I specify whether I use 7.0 or 7.1 ? within MS Visual Studio? or is it a matter of downloading a separate package?