Skip to content

A&A - Unhandled Rejection Error

Hi, just trying to figure out where to go to get help with an issue. My phone auto-updated and basically killed the app. I get this error and cannot do anything. I am fine waiting for the app to be updated, bit can I avoid all my games lapsing while they do? Many thanks!

Comments

  • bertmanbertman Member Posts: 2
    I’m have the same issue after then new iPad iOS update for 18.5
  • JuliusBorisovJuliusBorisov Member, Administrator, Moderator, Developer Posts: 22,815
    We’re still working on the issue, it’s getting closer. If you join Discord, you’ll be able to get a special role related to the issue and get notified once we start a test. https://discord.gg/QGBpdjptsT
  • brinstonebrinstone Member Posts: 2
    What I’ve seen related to the error: Game Fails to Load – PixiJS compressedImageParser Error

    Hi there,

    I’m experiencing an error preventing Axis & Allies 1942 Online from loading on some of my devices. The error message reads:

    Unhandled Rejection Error: compressedImageParser middleware for PixiJS v5 must be specified in loader.use() and must have resource.data when completed

    Here’s what I’ve observed:
    • The same app version works perfectly on my iPhone 13 (iOS 18.5).
    • The game stopped working on my iPad (also running the latest iPadOS).
    • A friend’s iPad runs the game fine, but the same error appears on his iPhone.
    • We’ve tested this on different networks (Wi-Fi and cellular), but the error persists.
    • We’ve both tried:
    • Powering off and restarting devices
    • Force-quitting the app
    • Deleting and reinstalling the app
    • Clearing app data (where possible)
    • My iPad has plenty of storage available (over 300 GB free).
    • All devices are on up-to-date OS versions.

    Based on the error text, it seems like the game might be missing a compressed texture asset, or there’s an issue with how the middleware is registered in PixiJS. It’s odd that the same version works on some devices but not others.

    Are there any additional steps I can try, or is there an update planned to resolve this?

    Thanks for your help
Sign In or Register to comment.