---
title: "Discussion on \"How I Released A Next JS App to the Google Play Store (with AWS Amplify)\" | Hashnode"
description: "Discussion on \"How I Released A Next JS App to the Google Play Store (with AWS Amplify)\". A Website I created for a Hackathon is now in Review for the Google Play Store."
url: "https://hashnode.com/posts/how-i-released-a-next-js-app-to-the-google-play-store-with-aws-amplify/60757e0085f3a21e3926ce37"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How I Released A Next JS App to the Google Play Store (with AWS Amplify)](https://blog.jarrodwatts.com/how-i-released-a-next-js-app-to-the-google-play-store-with-aws-amplify?utm_source=hashnode&utm_medium=feed)

A Website I created for a Hackathon is now in Review for the Google Play Store.

Apr 13, 2021 · 5 min read · blog.jarrodwatts.com  
Read the article

-   [#nextjs](https://hashnode.com/tag/nextjs)
-   [#aws](https://hashnode.com/tag/aws)
-   [#reactjs](https://hashnode.com/tag/reactjs)
-   [#app-development](https://hashnode.com/tag/app-development)
-   [#serverless](https://hashnode.com/tag/serverless)

## Written by

[Jarrod Watts](https://hashnode.com/@JarrodWatts)

@JarrodWatts · Sydney, Australia

  
[View profile](https://hashnode.com/@JarrodWatts)

Developer Relations Engineer @ Polygon Labs

A software engineer turned developer relations engineer in the web3 space, from Australia 🇦🇺.

## Responses 1

Markdown supported · ⌘↵ to post

[Satish Kumar Jaiswal](https://hashnode.com/@RichSatty)

[Jun 27, 2021](https://hashnode.com/posts/how-i-released-a-next-js-app-to-the-google-play-store-with-aws-amplify/60757e0085f3a21e3926ce37/comment/60d7d76ccb0aa8118c23bf25)

A nice article.

I recently faced a weird issue relevant to this and raised in stack overflow along with a support ticket to AWS. Do you think you can give some opinion on this. [StackOverflowPost](https://stackoverflow.com/questions/68134366/nextjs-pwa-ssr-enabled-apps-build-fails-through-aws-amplify)

[Satish Kumar Jaiswal](https://hashnode.com/@RichSatty)

[Jun 27, 2021](https://hashnode.com/posts/how-i-released-a-next-js-app-to-the-google-play-store-with-aws-amplify/60757e0085f3a21e3926ce37/comment/60d7d76ccb0aa8118c23bf25#reply-60d80a28de92ef110afdeaf3)

[Jarrod Watts](https://hashnode.com/@JarrodWatts)

Thanks mate for the reply. I even removed the image code and simply followed:

yarn create next-app --typescript

Configure Amplify and AWS

Use CI CD option to deploy to AWS via Amplify and link repository for the frontend app (ALL WORKS)

Configure next.config.js for PWA support using NextJS plugin called next-pwa Deploy again (BUILD FAILS)

[Satish Kumar Jaiswal](https://hashnode.com/@RichSatty)

[Jun 27, 2021](https://hashnode.com/posts/how-i-released-a-next-js-app-to-the-google-play-store-with-aws-amplify/60757e0085f3a21e3926ce37/comment/60d7d76ccb0aa8118c23bf25#reply-60d80b75cb0aa8118c23c279)

[Jarrod Watts](https://hashnode.com/@JarrodWatts)

Using Amplify just wanted more control rather using third party. In next.config.js, when reference to const withPWA = require(next-pwa) is removed, the issue is gone but loosing pwa support.

Amplify frustration is; it shows as 'internal error' within its logs and hence tough to identify the cause with insufficient documentation on Amplify pwa.

I even used 'next' version 10 that's as per docs is supported (limited).

[Satish Kumar Jaiswal](https://hashnode.com/@RichSatty)

[Jun 28, 2021](https://hashnode.com/posts/how-i-released-a-next-js-app-to-the-google-play-store-with-aws-amplify/60757e0085f3a21e3926ce37/comment/60d7d76ccb0aa8118c23bf25#reply-60d9c78b68364a2e7b2ce75a)

[Jarrod Watts](https://hashnode.com/@JarrodWatts) Finally, It's 9.x.x that worked but still would wait AWS response because that means NextJS latest version vs AWS supported will lag behind to use features like Image component from the latest NextJS version.
