Windows App Certification Kit: Failed - SOLVED

Hi,

Can anyone help with this please:

Code (CSharp):

1. Supported API test
2.  
3. FAILED
4.     Supported APIs
5.  
6.     Error Found: The supported APIs test detected the following errors:
7.         This API is not supported for this application type - Api=System.String.Format(System.String,System.Object). Module=MSCORLIB, PUBLICKEYTOKEN=7CEC85D7BEA7798E. File=UnityEngine.dll.
8.     Impact if not fixed: Using an API that is not part of the Windows SDK for Windows Phone Store apps violates the Windows Phone Store certification requirements.
9.     How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Windows Phone Store app. Please note, C++ apps that are built in a debug configuration will fail this test even if they only use APIs from the Windows SDK for Windows Phone Store apps

Is this a Unity issue?

 

I'm still going to try and attempt to upload my game to the store and see if I get it rejected or not over this issue. I hope this does not matter as my game is already on all other platforms without any issues.
I let you know the results etc.

 

Hi,

I already reported the issue and it should be already fixed and coming to next version. Unfortunately your game will be rejected in windows store (and windows phone store also).

The issue: http://fogbugz.unity3d.com/default.asp?642901_ul237g03pbf89b1o

 

Thanks, yes it just got rejected.

I'm really getting pissed of recently with Unity, is this a joke, each time next version it be fixed blah blah.
These are show stopper bugs, it means our applications cannot be submitted to the stores and this makes hard work pointless and delays everything.

BTW I'm using also 4.6b21, its about time they released 4.6b22 or Unity 5b12 as currently 4.6beta21 useless as no patch for this included, 5b11 useless as no GUI included. Really becoming a mess.

Rant over anyway but I make a damn good point.

Edit: You should reply to the ticket asking for a date!

 

Cool, thank you Tautvydas, that has given me some hope and look forward to the build.
Cheers.

 

Thanks, I can confirm the latest 4.6C1 has the fix and working correctly.