Hello World App Error - Something Went Wrong

[joshb45495208]

When trying to do a hello world of a Firefly app, I am able to install the app using the Adobe I/O CLI, that works fine now.

But when I run `aio app run` and open both the localhost URL and the experience cloud URL, I get the following error:

 

I haven't modified any code.

Here are the errors in the browser console:

localhost:

 

experience cloud:

 

 

[duypnguyen]

Did you change some code from the default template? Could you please share the modified code fragment and what errors you got from the browser console?

[joshb45495208]

I haven't modified any code, just done the aio app init and then aio app run.

[joshb45495208]

I've added screenshots of the browser console to the question.

[duypnguyen]

These are helpful, thanks!

Could you please share:

• which options you selected during app init
• output of `aio info`

[joshb45495208]

Options selected during app init:

➜ ~ aio app init firefly_hello_world2
(node:70468) ExperimentalWarning: Conditional exports is an experimental feature. This feature could change at any time
Retrieving information from Adobe I/O Console..
? Select Org Blast Analytics and Marketing Partner Sandbox
? Select Project Project Firefly Test
? Select Workspace Production
create console.json

You are about to initialize the project 'HonCrimsonShark'
Generating code in: /Users/joshuabarratt/firefly_hello_world2
? Which Adobe I/O App features do you want to enable for this project?
select components to include Actions: Deploy Runtime actions, Events: Publish to Adobe I/O Events, Web Assets: Deploy hosted static assets, CI/CD: Include GitHub Actions based workflows for Build, Test and Deploy
? Which type of sample actions do you want to create?
select type of actions to generate Adobe Analytics, Generic
? We are about to create a new sample action that interacts with the Adobe Analytics API
how would you like to name this action? analytics
? We are about to create a new sample action that showcases how to access an external API
how would you like to name this action? generic
? We are about to create a new sample action that creates messages in cloud events format and publishes to Adobe I/O Events
how would you like to name this action? publish-events

Output of aio info:

➜ firefly_hello_world2 aio info

System:
OS: macOS 10.15.5
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 4.48 GB / 32.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 13.8.0 - /usr/local/bin/node
Yarn: Not Found
npm: 6.13.7 - /usr/local/bin/npm
Virtualization:
Docker: Not Found
npmGlobalPackages:
@adobe/aio-cli: 3.6.0
CLI plugins:
@adobe/aio-cli 3.6.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-help 2.2.3 (core)
@oclif/plugin-autocomplete 0.2.0 (core)
@adobe/aio-cli-plugin-config 2.2.1 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@adobe/aio-cli-plugin-console 3.1.0 (core)
@adobe/aio-cli-plugin-app 3.0.1 (core)
@adobe/aio-cli-plugin-auth 2.2.0 (core)
@oclif/plugin-plugins 1.8.0 (core)
@adobe/aio-cli-plugin-certificate 0.2.0 (core)
@adobe/aio-cli-plugin-info 1.0.0 (core)
@adobe/aio-cli-plugin-runtime 1.8.0 (core)
@adobe/aio-cli-plugin-events 1.0.0 (core)

[duypnguyen]

I can see that you have node v13 in your machine. We don't support odd versions as they are experimental and may break some libraries. Could you please try node v10 or v12?

More on this: https://github.com/AdobeDocs/project-firefly/blob/master/getting_started/setup.md#required-tools

[joshb45495208]

Exactly the same issue when using node v12.13.0

firefly aio info

System:
OS: macOS 10.15.5
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 1.65 GB / 32.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.13.0 - ~/.nvm/versions/node/v12.13.0/bin/node
Yarn: Not Found
npm: 6.12.0 - ~/.nvm/versions/node/v12.13.0/bin/npm
Virtualization:
Docker: Not Found
npmGlobalPackages:
@adobe/aio-cli: Not Found
CLI plugins:
@adobe/aio-cli 3.6.0 (core)
@oclif/plugin-help 2.2.3 (core)
@oclif/plugin-plugins 1.8.0 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@adobe/aio-cli-plugin-config 2.2.1 (core)
@oclif/plugin-autocomplete 0.2.0 (core)
@adobe/aio-cli-plugin-console 3.1.0 (core)
@adobe/aio-cli-plugin-auth 2.2.0 (core)
@adobe/aio-cli-plugin-app 3.0.1 (core)
@adobe/aio-cli-plugin-certificate 0.2.0 (core)
@adobe/aio-cli-plugin-info 1.0.0 (core)
@adobe/aio-cli-plugin-runtime 1.8.0 (core)
@adobe/aio-cli-plugin-events 1.0.0 (core)

[duypnguyen]

Our team was able to reproduce your error and is now investigating further. We will update you once issue is fixed.

[joshb45495208]

Super, thanks for the update

[Meryll_Blanchet]

Hi Josh,

We created https://github.com/adobe/aio-cli-plugin-app/issues/263

You'll be able to follow the resolution there.

Cheers,

Meryll

[joshb45495208]

Thanks, I've subscribed to the issue on Github.

[dr_venture]

confirmed.

[Meryll_Blanchet · Accepted solution]

Hi Josh,

While we are working on a fix (see https://github.com/adobe/aio-cli-plugin-app/issues/263), here's a workaround that you can try locally:

- Clean your browser cache

- Go into your bootstrapped app folder

- rm -rf package-lock.json node_modules

- Edit the package json file and make sure that these dependencies are in with these locked versions:

    "regenerator-runtime": "^0.13.5",
    "@adobe/exc-app": "^0.2.14",
    "@react-spectrum/button": "3.0.0-rc.3",
    "@react-spectrum/form": "3.0.0-rc.3",
    "@react-spectrum/layout": "3.0.0-rc.0",
    "@react-spectrum/link": "3.0.0-rc.0",
    "@react-spectrum/picker": "3.0.0-rc.0",
    "@react-spectrum/progress": "3.0.0-rc.3",
    "@react-spectrum/provider": "3.0.0-rc.3",
    "@react-spectrum/text": "3.0.0-rc.0",
    "@react-spectrum/textfield": "3.0.0-rc.3",
    "@react-spectrum/theme-default": "3.0.0-rc.3"

- npm i

- aio app deploy

The SPA should deploy and load as expected.

Thanks for reporting this issue and for your patience.

Cheers,

Meryll

[SarahXu]

@joshb45495208 this should be fixed now! please refer to the issue linked for more details.

[joshb45495208]

Thank you, it's working now.