Advertisement
Australia markets closed

  • ALL ORDS

    7,937.50
    -0.40 (-0.01%)
     

  • ASX 200

    7,683.00
    -0.50 (-0.01%)
     

  • AUD/USD

    0.6512
    +0.0012 (+0.18%)
     

  • OIL

    82.95
    +0.14 (+0.17%)
     

  • GOLD

    2,329.00
    -9.40 (-0.40%)
     

  • Bitcoin AUD

    98,820.54
    -3,667.68 (-3.58%)
     

  • CMC Crypto 200

    1,389.04
    -35.06 (-2.46%)
     

  • AUD/EUR

    0.6077
    +0.0006 (+0.10%)
     

  • AUD/NZD

    1.0953
    +0.0011 (+0.10%)
     

  • NZX 50

    11,946.43
    +143.15 (+1.21%)
     

  • NASDAQ

    17,526.80
    +55.33 (+0.32%)
     

  • FTSE

    8,040.38
    -4.43 (-0.06%)
     

  • Dow Jones

    38,460.92
    -42.77 (-0.11%)
     

  • DAX

    18,088.70
    -48.95 (-0.27%)
     

  • Hang Seng

    17,277.56
    +76.29 (+0.44%)
     

  • NIKKEI 225

    37,636.21
    -823.87 (-2.14%)
     

Amazon's Appstore is finally working again on Android 12

The marketplace had been malfunctioning for more than a month.

Igor Bonifacic
·Contributing Reporter
·1-min read
Cherlynn Low / Engadget

Amazon has addressed the issue that had left those with Android 12 phones unable to use apps they had downloaded from the company's Appstore. “We have released a fix for an issue impacting app launches for Amazon Appstore customers that have upgraded to Android 12 on their mobile devices," a spokesperson for the company told Engadget on Friday. "We are contacting customers with steps to update their Appstore experience. We are sorry for any disruption this has caused.”

Reports of applications from the Appstore not working on Android 12 started to surface online in late October. Those with devices like the Google Pixel 6 and Samsung Galaxy S21 found they couldn't run any of the software they had previously downloaded from the Appstore. There were also reports of no apps showing up in the marketplace. While the issue didn't affect many people, it took about a month for Amazon to acknowledge it officially. On Friday, the company didn't say what had caused the problem. When it first surfaced, there was speculation it stemmed from an incompatibility between Amazon's built-in DRM and Android 12.