No Assets

Issue #80 closed
Wapu Kashuken created an issue

no assets available after updating any or all characters.

don't know if this is a bug, or has not been activated yet for this version.

Comments (8)

  1. Evanova Android repo owner

    The way this bug works is:

    • Capsuleer Alice is loaded with the API keys. Not all information is fetched for performance sake. That includes all the CacheProvider.getCachedResponse() clients.

    • Alice is selected, going straight to the Asset list: ContentServiceImpl relies on CacheProvider.getCachedResponse() but CacheProvider claims it has nothing cached for assets. This is true since we didn't fully reload Alice yet and ContentServiceXXX caches an empty collection of assets.

    • Subsequent trials to display the assets show the empty list because it's cached. This is also true after reloading a character. The result is, although the cache now has the assets, they still don't show up.

    • Trying to fully reload Alice before going to the Assets view shows the assets correctly.

    The following scenario should show assets correctly.

    • Make sure Evanova is not running.
    • Start Evanova, select Alice.
    • Hit the reload button and wait until it's done.
    • Go the assets view, assets should show up correctly.

    This should not show the assets correctly, after a reload:

    • Make sure Evanova is not running.

    • Start Evanova, select Alice.

    • Go the assets view. The asset view should be blank.

    • Go back, hit the reload button and wait until it's done.

    • Go the assets view, assets should show nothing as an empty list is cached.

  2. Wapu Kashuken reporter

    Yup... so after doing this, assets now show for all toons.

    Bigger problem is... Evanova runs as a service, so technically its always running.

  3. Evanova Android repo owner

    Evanova's back-end is designed to not be a persistent service. The Service behind most of API calls should go away (be destroyed) when there is no job to perform.

    A lot of work has been done recently for this release on this particular point, so shoot up any log/stat you have!

  4. Log in to comment