Since the release of iOS 7, we have seen an increase of reports, particularly on older devices (iPad 1 and iPad 2) where Knots 3D (v3.3.x) gets into a bad state. Reports show this happening occasionally on the Language Selection screen. We think we have isolated the problem and a fix will be available in the next release due out within the next few weeks. In the meantime, the following instructions should resolve this and similar issues should they occur:
“Kill” the app and restart it, the problem will go away and most likely you won’t ever see it again.
If you are unsure how to “kill” an app, it is as follows:
iOS6:
– Press the physical home button once to exit Knots 3D
– Press the physical home button twice to see a list (across the bottom of the screen) of apps in memory
– Hold your finger down on the Knots 3D icon until it starts to “jump”
– Press the “-” sign. This stops the app from running (removes it from memory but does not remove it from your device). You might want to stop other apps you are no longer using while you are at it.
– Restart Knots 3D in the usual way
iOS7:
– Press the physical home button once to exit Knots 3D
– Press the physical home button twice to see thumbnail views of apps in memory
– “Flick” (swipe up) the Knots 3D view up with your finger to remove it from memory (This stops the app from running e.g. removes it from memory but does not remove it from your device. You might want to stop other apps you are no longer using at the moment while you are at it.)
– Restart Knots 3D in the usual way
Android:
Follow the instructions on this site: How To Geek: How to force kill android applications without a task manager
Please contact us if this does not resolve the problem.
There have been several reports that Knots 3D will not install on some older Samsung devices due to cache limitations on these devices. The devices I am aware of are Samsung Captivate and Samsung Galaxy S. The Samsung Captivate is AT&T’s version of the Samsung Galaxy S.
Other Variants of Samsung Galaxy S (Released Early 2010):
- Samsung Captivate (ATT)
- Samsung Epic 4G (Sprint)
- Samsung Fascinate (Verizon)
- Samsung Vibrant (T-Mobile)
The error message some people are getting: “Error Downloading Insufficient space on device”
This error comes despite plenty of free space on both external and internal storage ie > 1GB. Since Knots 3D is around 33MB at present, why this error message? Well, it turns out that the memory the error message is referring to is the cache partition. The cache size limit on these Samsung devices is 30MB. This means any app, including ours, larger than 30MB, is more than likely seeing this issue. This is a device specific environment thing and completely outside the control of Knots 3D, Google Play, Amazon, etc. There is nothing we can do although a possible workaround (try at your own risk) is mentioned in a link below. If the free version (13MB) of Knots 3D is installing successfully, then that also confirms this might be the cause of the problem.
Some links discussing the issue:
http://stackoverflow.com/questions/4850889/people-cant-download-our-specific-product-in-android-market
http://androidforums.com/captivate-support-troubleshooting/419535-2-3-3-gb-cache-limit.html
http://forum.xda-developers.com/showthread.php?t=1006268
Possible work around found here (try at your own risk):
http://forum.xda-developers.com/showpost.php?p=17889343&postcount=2011
We received an email from Google Play yesterday indicating that certain apps on certain devices were failing to launch due to an issue within Google Play. Google has resolved the issue but requires all of the affected apps to be re-released with an incremented version number. A copy of the Service Notification has been pasted below. This is strictly a Google Play issue and does not affect the other app stores (iTunes, Amazon, BN).
We have updated both Knots 3D (v2.8.1) and Knots 3D – Free Knot Edition (v1.1.1) on Google Play and they should be available shortly.
Subject: Google Play Service Notification: APK update required for your apps
Dear Google Play developer,
We have identified one or more of your applications as being affected by a recent issue in Google Play that prevents some users from launching your app. To resolve the issue, you need to publish an update as soon as possible. This will cause your users to receive an update, which will fix the issue.
The underlying cause was an error in the Google Play update logic that resulted in native libraries being incorrectly installed during updates of affected applications for users running Android 4.1 (Jellybean), who installed an update of your application between August 1 to August 5. This affects a small minority of applications, specifically non-forward-locked paid applications that use the NDK and native libraries.
No change to your application is required. Simply increment your versionCode in your Android manifest file, generate a new APK, and publish it through Google Play.
We apologize for the inconvenience this has caused you and your users. The underlying cause has now been rectified, and steps have been taken to ensure similar issues don’t arise in the future.
Sincerely,
The Google Play team© 2012 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
You have received this mandatory email service announcement to update you about important issues regarding your Google Play publisher account and published applications.
