kandi X-RAY | playn Summary
kandi X-RAY | playn Summary
PlayN is a cross-platform Java game development library written in Java that targets HTML5 browsers (via GWT), desktop JVMs, Android and iOS devices.
Top functions reviewed by kandi - BETA
- Returns the Key corresponding to the given key .
- Translate a key code .
- Returns a string representation of the specified type .
- Advances the JSON token .
- Sends a request .
- Prepare the draw .
- Handles a MotionEvent .
- Generate the cache manifest .
- Execute Xhr request .
- Loads the audio file from the specified file .
playn Key Features
playn Examples and Code Snippets
Trending Discussions on playn
I have a little game application Deal-O-Round in the Google Play Store and I submitted the same APK about 7 years ago (July 6, 2014 https://smile.amazon.com/Csaba-Toth-Deal-O-Round/dp/B00LK8VBLS/) to the Amazon Mobile Marketplace as well. The 2014 version was based on Google PlayN framework which allowed a web-based demo as well besides Android and iOS platforms. A lot of time passed and last year I re-implemented the whole game in Flutter, which also allows the build of a web-based demo besides Android and iOS.
Even more recently I got an email from Amazon with the title "[ACTION REQUIRED] App update required for target API Level compliance" which nudged me to try to refresh the APK in their store again. According to the email the Fire OS 6 releases require minimum API level 25 and Fire OS 7 will require minimum API level 28. That's great news, I refreshed my Flutter project and the Gradle upgrade bumped the min SDK API level to 23. And my current target API level is 29 as seen in my build.gradle. Everything is open source BTW....
ANSWERAnswered 2021-Mar-30 at 18:36
I went back to the page I took the screenshot from. On the first ("Amazon Fire Tablets and Phones") and the last ("Non-Amazon Devices") tab all the little question marks show a "Targeted by another APK in the current version." hint. I'll need to research that more because it sounds nonsensical. The "Amazon Fire TV" tab's hints show some
minSdkVersion (for very old devices) and also
"android.hardware.touchscreen" capability hint. My game needs touch screen, so that's not surprising and the old APK wasn't supporting those either.
Reading more about the
Targeted by another APK in the current version. hint I came across https://developer.amazon.com/docs/app-submission/publish-app-upload-apk-files.html#add_multiple_apks
"With the second APK, you can select support for devices not already selected by the first APK.". I'm not sure why the store is not able to serve automatically the more recent APK and why I have to manually toggle things, but well, that's what I'll do.
- Starting edit:
- Turning off devices for the old APK
- Turing off on the other tab for the old APK:
- Editing and turning on devices for the newer APK. Maybe this is why there's this weird thing going on, I have to decrease minSdk back from 23 to 22 to have a better coverage:
USE_CREDENTIALS is not a problem supposedly (so far). If the above doesn't help to you then also check out https://developer.amazon.com/docs/app-submission/troubleshooting-android-manifest-and-device-targeting.html
No vulnerabilities reported
You can use playn like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the playn component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
Reuse Trending Solutions
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page