Im actually facing a problem on submitting an app to Firefox OS marketplace.Recently i developed an HTML5 game using construct 2 and tested it on the Simulator using App manager, and submitted the app on the firefos marketplace.It passed all validation checks, however the reviewer said game stops loading on Firefox OS 1.1,so i was rejected!
Now i have then tested it on Simulator for 1.1, and the game stops loading.
So the problem is with OS 1.1 , other than that the game works fine, esp with OS 2.0
Now , can i submit the game only for versions above 1.1??
I dont want the app to run on 1.1, i just want to submit it for versions higher versions.
Is it possible?? any help??
Thanks in advance
Actually mostly reviewers will be using Firefox OS 1.1 to test the application because it is widely used.
If you have written the working app you can mention the simulator in which you have tested or can tell the device OS version you have used. So other reviewers will know and wont reject the app.
PS:- Try to use the target development environment as Firefox 2.0 in mid of 2015 and as of now Firefox 1.3 and above as many people have 1.1 and above.
Some apps state in their descriptions the minimum version required for it to work. For example: https://marketplace.firefox.com/app/recorder and https://marketplace.firefox.com/app/copy-paste-keyboard.
Related
I am very new in using Primefaces. I & our team planning to write Web Application that need to be running on Web Browser on both Windows OS and Mac OS . Here are my questions that need help for the answers :
(1) Can we develop Web Application be able to run on Web Browser on both Windows OS and Mac OS ?
(2) What are Web Browsers on Windows OS that Primefaces support ? Which ones are the most compatible ?
(3) What are Web Browsers on Mac OS that Primefaces support ? Which ones are the most compatible ?
Thank you very much in advance.
Best Regards
Pearapon
Bangkok, Thailand
I would suggest the following: create a test primefaces application which contains all component that your application will use (even better if you test also nesting the components) with a mocked backend. Then test your test ui in all desired browsers on desired platforms but on differents OS it shouldn't be different. I only work with windows but I test the application on Chrome, Firefox, IE, Safari and Opera. The only significant problems I faced was with CSS. E. g. a component does not use the full width etc.
Since submitting a Windows Phone 8.1 app alongside our Windows Phone 8 I've noticed some strange behaviour in the store regarding app version numbers. In my AppManifest and when I'm building packages for the store I set a version number say, 2.0.2.1.
The package uploads fine but when visible in the store and on the upload page the version number has changed to when I built the package, for example v2015.918.xxxxx = 18/9/2015. I guess this is fine as it will keep getting larger but I still rather show the actual version number.
Thanks to an automated Twitter account I've noticed it happening to other apps too: https://twitter.com/NewsCuriosityWP/status/646956803079700480
I'd love to know why this happening, a bug with the store maybe?
Here are some examples:
I had this problem too, I posted about it in the forums: https://social.msdn.microsoft.com/Forums/en-US/d2913ad6-6130-45b6-8a7f-086ff7f04cff/problem-with-version-number?forum=wpsubmit
Apparently it is working as intended ... but when I ported an app to Win10 UWP, it really messed up the version numbers and now I have to specify a version starting with 2015.... :-(
If you want to avoid this for new applications, you can prevent it from creating an app bundle, and then it should use the version number you specified.
Unfortunately, for already published app you cannot go back from app bundling
Hope this helps...
When testing using Flash CC 2014, I get an error Functions called in incorrect sequence, or earlier call was unsuccessful.
Does this feature require the actual iOS or Android device to test, or can it be tested without it?
No, you can also test it using the iOS Simulator as well and possibly the Android Simulator, if you can get that working (I never bother with the Android simulator, though, even when working with native development). You cannot test it using the AIR Simulator, though. The camera functionality requires native APIs to function.
Also, keep in mind that the CameraRoll (and camera functionality in general) varies by platform. Do not assume that because you tested it on an Android device, it will work properly on an iOS device or vice versa. You must test it on all supported platforms.
While looking over the Adobe Flash Player/AIR Roadmap (found here) I saw this:
"Flash Player release and debug players are available and supported for Windows 8 Desktop and Modern UI experiences on both x86/64 and ARM platforms."
Which got me thinking about a potential method that apps for Windows 8 might be able to be released using Flash Player.
Currently, using AIR, you can build apps for Android and iOS, as well as for Windows Desktop. But Windows 8 Modern UI and Windows Phone 8 are both unsupported platforms.
So the idea was this. If IE 10 for Modern UI supports Flash Player, and if HTML5 Modern UI Windows apps use IE under the hood in order to run, then supposedly you could wrap a Flash Player app inside of an HTML5 app, and then, voilà, you'd have a Windows Modern UI app running off of ActionScript. (Though it still wouldn't work for Windows Phone 8.)
Well, I have tested this, and (sadly) it doesn't work. I would almost bet that this isn't because the functionality isn't there, but rather it is because of some switch on the backend that prevents this functionality from being used.
So, finally, here is my question, mainly to sate my curiosity on the subject. Does anyone know whether or not such a backend switch exists, and if so, is there a way to switch it?
I have tried the same thing as you and no, I don't think such a switch exists.
I can only assume Microsoft has purposely blocked off ActiveX controls on purpose, since Silverlight also does not work in HTML5 apps.
It is sort of possible that with Windows 8.1 Update 1, they may change this, but I believe it opens up a lot of problems for them from a security / app store catalogue perspective, so would be unlikely.
I'm porting a HTML-based app to a Samsung smart TV. The app uses local storage to keep preferences, etc.. Local storage appears to be supported and data is persistent while the browser is open. But, once the browser is exited ... poof! the data is gone. Other data like sessions and cookies do persist.
I use the Lawnchair library in the app and have also tested using jStorage. Neither persist beyond closing of the browser.
The browser (or browser component) on the TV is webkit build 534.7. From playing with the browser, I suspect it is actually written in Adobe Air.
I have also tested the Air browser component on my PC, which is build 533.19.4 of webkit. This doesn't appear to support local storage at all.
Chrome on my PC, build 535.19 of webkit, works fine in all my tests.
So, where does the blame lie here: is it the webkit build, the implementation of webkit in Adobe Air, or the TV? Can anyone offer a fix or a suggestion for work around?
Thanks.
Unfortunately I don't have 2012 model so I can't check if the HTML5 localStorage is working or not.
But I have workaround for you which will be backward compatible with previous TV sets' models also, as 2010 and 2011 models use Maple browser:
http://www.samsungdforum.com/Guide/View/Developer_Documentation/Samsung_SmartTV_Developer_Documentation_3.1/API_Reference/JavaScript_APIs/File_API
Serialize your data object
Save it using File API to application directory
And every time you open the app open this file and unserialize data.
This will work for sure!
1- you an use file api
2- you can set a cookie
I was once trying to save preferences of my app and using cookies seemed easier.
I don't know much about html5 but in TV's you should check which features allowed. Most of the smart tv's are giving partial support to html5.