Difference between revisions of "Bugs"
Jump to navigation
Jump to search
(shouldnt exist anymore, as long as their validating-integrity-through-hashes-and-sizes is thorough) |
|||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
This page <em>may</em> overlap with the official list of bugs here: https://housamo.info/news/bugfix/. | |||
= Android 9 = | |||
Starting with app version 3.4.5, the app currently hangs when trying to download assets from the CDN. Due to the CDN using plaintext HTTP (not HTTPS), the app hangs because of recent security setting changes with Android 9, as per https://developer.android.com/training/articles/security-config#CleartextTrafficPermitted. The current hotfix would be to manually patch the APK itself through private, undisclosed means. This has been acknowledged by LW and a fix will happen soon. | |||
=Forced Battle Exit= | |||
It's currently unknown if this is an actual issue. | |||
During a battle, after restarting the app an unknown amount of times (a lot), and restarting (and/or resuming from last turn), the app may outright ignore the battle and instead kick you straight to the main screen. It is unknown if restarting the app on the same device is good enough, but using a different device will resume the battle just fine. In short, the app may, on the client side, force exit a battle after a certain amount of app resets. | |||
Further tests are needed to verify this. | |||
=Game Stuck On Downloading= | =Game Stuck On Downloading= | ||
{|style="float:right;" | {|style="float:right;" | ||
| Line 13: | Line 22: | ||
* Relaunch the app, or copy AuthKey to <code>/SD/Android/data/jp.co.lifewonders.housamo/files/Data/AuthKey</code> | * Relaunch the app, or copy AuthKey to <code>/SD/Android/data/jp.co.lifewonders.housamo/files/Data/AuthKey</code> | ||
You may be able to get away with removing the cache and MasterDataVersions, but an almost clean slate will do. | You may be able to get away with removing the cache and MasterDataVersions, but an almost clean slate will do. | ||
=Cache-related Soft Lock= | <!--=Cache-related Soft Lock= | ||
<s>During a charge animation, if the game doesn't have the images for characters cached, the game soft locks. This is (probably) due to the game process the animation faster than it could cache the textures (due to a slow internet connection or server stress), causing it to try to shrink empty textures. The devs could avoid this by implementing a universal missing texture (such as the pink checkerboard Source uses) as a placeholder for missing assets. As for a temporary hot fix right now, the end user could slow down the game speed (either by the in-battle option, or for cease usage of game tuning apps that reduce the internal rendering resolution to reduce frame time).</s> | <s>During a charge animation, if the game doesn't have the images for characters cached, the game soft locks. This is (probably) due to the game process the animation faster than it could cache the textures (due to a slow internet connection or server stress), causing it to try to shrink empty textures. The devs could avoid this by implementing a universal missing texture (such as the pink checkerboard Source uses) as a placeholder for missing assets. As for a temporary hot fix right now, the end user could slow down the game speed (either by the in-battle option, or for cease usage of game tuning apps that reduce the internal rendering resolution to reduce frame time).</s> | ||
This issue seemed to be fixed through a change in how animations are played, as well as predownloading assets before the start of phase 1. | This issue seemed to be fixed through a change in how animations are played, as well as predownloading assets before the start of phase 1.--> | ||
= | <!--=Web Page Soft Lock= | ||
<s>On Android, locking your device or swapping apps while a web page is loaded in-app (such as an event or a gacha list) will cause the page to be unable to close, requiring relaunching the app.</s> | |||
This has been fixed by forcing the web object to be closed instantly the game's OnApplicationPause event is invoked.--> | |||
Latest revision as of 06:47, 18 March 2019
This page may overlap with the official list of bugs here: https://housamo.info/news/bugfix/.
Android 9
Starting with app version 3.4.5, the app currently hangs when trying to download assets from the CDN. Due to the CDN using plaintext HTTP (not HTTPS), the app hangs because of recent security setting changes with Android 9, as per https://developer.android.com/training/articles/security-config#CleartextTrafficPermitted. The current hotfix would be to manually patch the APK itself through private, undisclosed means. This has been acknowledged by LW and a fix will happen soon.
Forced Battle Exit
It's currently unknown if this is an actual issue.
During a battle, after restarting the app an unknown amount of times (a lot), and restarting (and/or resuming from last turn), the app may outright ignore the battle and instead kick you straight to the main screen. It is unknown if restarting the app on the same device is good enough, but using a different device will resume the battle just fine. In short, the app may, on the client side, force exit a battle after a certain amount of app resets.
Further tests are needed to verify this.
Game Stuck On Downloading
|
|
Whether it's an app or Android update, sometimes the game will refuse to progress after allegedly downloading. The go-to fix is:
- Backup AuthKey:
/SD/Android/data/jp.co.lifewonders.housamo/files/Data/AuthKey - Remove
/SD/Android/data/jp.co.lifewonders.housamo/files/(or every other folder except/SD/Android/data/jp.co.lifewonders.housamo/files/Data/) - If you're keeping
/SD/Android/data/jp.co.lifewonders.housamo/files/Data/, remove/SD/Android/data/jp.co.lifewonders.housamo/files/Data/MasterDataVersions - Remove
/SD/Android/data/jp.co.lifewonders.housamo/files/ - Remove
/SD/Android/data/jp.co.lifewonders.housamo/cache - Relaunch the app, or copy AuthKey to
/SD/Android/data/jp.co.lifewonders.housamo/files/Data/AuthKey
You may be able to get away with removing the cache and MasterDataVersions, but an almost clean slate will do.