Shopify / Shopify/shopify-app-template-node

Installed app doesn't display UI on store

Open
#1,288 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1k
Forks
434
PR merge metrics
No merged PRs in 30d

Description

Issue summary

I am currently in deployment stage of my shopify app. Everyhting is working fine in development and there are no issues with getting the app running onto my development store.

I am now deploying the app on fly.io. The image gets built on fly fine and the machine gets deployed all good. I go to install the app, it sends me to the install screen all good, then when it comes to going to the home screen of the app, it doesnt show anything and comes up with this error in the console:
Screenshot 2023-07-13 at 12 09 48 pm
Screenshot 2023-07-13 at 12 58 03 pm

Upon further inspection, I have been able to see that this file is in the path /frontend/dist/assets/index-28a6294e.js. It seems like this file gets generated when npm installs dependencies in the build and on production as the suffix of the file refers to the commit hash of the latest commit on the repo.

I hope this is enough information for anyone to be of any assistance. Would greatly appreciate any sort of help as this is literally the last part I need to complete for the app to be working and I am at a loss as to what I should do.

  • @shopify/shopify-app-express version: N/A
  • Node version: N/A
  • Operating system: macOs Ventura
Uncaught TypeError: t is not a constructor
    at b8 (index-28a6294e.js:83:23985)
    at Z (index-28a6294e.js:97:796)
    at index-28a6294e.js:73:88558
    at index-28a6294e.js:1:23
    at index-28a6294e.js:113:19716

Expected behavior

The app should be loading onto the screen

Actual behavior

The app does not load and just shows a blank screen
image

Steps to reproduce the problem

  1. Deploy app to fly.io as per instrcutions
  2. Build docker image through deployment
  3. Install app onto store

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the deployed /frontend/dist/assets/index-28a6294e.js bundle and the browser error Uncaught TypeError: t is not a constructor at the reported locations. Compare the Fly.io Docker build with the development build and verify the app loads after installation without a blank screen.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, javascript, react
Domain
devops, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.