Skip to content

memory-footprint: fail with missing assets #52

@ithinkihaveacat

Description

@ithinkihaveacat

The memory footprint tool fails if the APK has missing assets. It would be helpful if it could ignore the missing asset and calculate the memory footprint anyway (since at least in some cases, these watch faces run on devices just fine).

$ java -jar ./memory-footprint/build/libs/memory-footprint.jar \
        --schema-version 2 \
        --ambient-limit-mb 10 \
        --active-limit-mb 100 \
        --apply-v1-offload-limitations \
        --estimate-optimization \
        --watch-face watchface.apk
Starting memory footprint test with watchface.apk
2024-09-23 18:00:48.593 java[24701:1169791] WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
Test report:
[MEMORY_FOOTPRINT]: ❌FAIL❌ Asset @background/wfs_logo31_80002c3c_88d1_4c42_a63a_c21c1bf3371a was not found in the watch face package ❌ 

Example APK: https://drive.google.com/file/d/1EiHq8u53o4tBtwYvFshKo_isefp2nSVa/view?usp=drive_link

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions