Build Errors (Assets Archive URL & JSX Component)

Hi everyone,

Received the error message below twice when trying to build a web app. Has anyone else encountered these errors and can give some insight on how to address them?

Best,

cffj

Runtime version: 4.9.72;
AB version: 1.7.11
COMMAND:

ASSETS_ARCHIVE_URL=https://appgyver-meap-assets.s3.amazonaws.com/fxzg12la4h4i1noihltk7bxopp4l?response-content-disposition=attachment%3B%20filename%3D"assets.zip"%3B%20filename*%3DUTF-8’'assets.zip&response-content-type=application%2Fzip&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJJSXXQRL4UNGBAXQ%2F20230918%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230918T210019Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=91c1ca4efffa3276866529e8619731d49b41d518b3df1548075478ed5b06ccfb NODE_OPTIONS=–max-old-space-size=10240 dockerrun --rm -v /home/ec2-user/builds/312806-web-298676:/app:z -v /home/ec2-user/.npmrc:/home/node/.npmrc web ash -c ‘NODE_OPTIONS=“–max-old-space-size=10240” NEXT_SUPPORT_RELATIVE_PATHS=true ASSETS_ARCHIVE_URL=“https://appgyver-meap-assets.s3.amazonaws.com/fxzg12la4h4i1noihltk7bxopp4l?response-content-disposition=attachment%3B%20filename%3D"assets.zip"%3B%20filename*%3DUTF-8’'assets.zip&response-content-type=application%2Fzip&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJJSXXQRL4UNGBAXQ%2F20230918%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230918T210019Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=91c1ca4efffa3276866529e8619731d49b41d518b3df1548075478ed5b06ccfb” npx rnv export -p web -s standalone -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @appgyver/orchestra-template-standalone@4.9.72 -r’

FAILED with ERROR:

│ [ error ] [build] COMMAND:
npx next build
FAILED with ERROR:
Type error: ‘View’ cannot be used as a JSX component.
Its instance type ‘View’ is not a valid JSX element.
The types returned by ‘render()’ are incompatible between these types.
Type ‘import(“/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index”).ReactNode’ is not assignable to type ‘React.ReactNode’.
Type ‘ReactElement<any, string | JSXElementConstructor>’ is not assignable to type ‘ReactNode’.
Property ‘children’ is missing in type ‘ReactElement<any, string | JSXElementConstructor>’ but required in type ‘ReactPortal’.
Type error: ‘View’ cannot be used as a JSX component.
Its instance type ‘View’ is not a valid JSX element.
The types returned by ‘render()’ are incompatible between these types.
Type ‘import(“/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index”).ReactNode’ is not assignable to type ‘React.ReactNode’.
Type ‘ReactElement<any, string | JSXElementConstructor>’ is not assignable to type ‘ReactNode’.
Property ‘children’ is missing in type ‘ReactElement<any, string | JSXElementConstructor>’ but required in type ‘ReactPortal’.
Type error: ‘View’ cannot be used as a JSX component.
Its instance type ‘View’ is not a valid JSX element.
The types returned by ‘render()’ are incompatible between these types.
Type ‘import(“/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index”).ReactNode’ is not assignable to type ‘React.ReactNode’.
Type ‘ReactElement<any, string | JSXElementConstructor>’ is not assignable to type ‘ReactNode’.
Property ‘children’ is missing in type ‘ReactElement<any, string | JSXElementConstructor>’ but required in type ‘ReactPortal’.
Error: Command failed with exit code 1: npx next build
Failed to compile.
./src/components/App/AppSwitcher.tsx:9:6
Type error: ‘View’ cannot be used as a JSX component.
Its instance type ‘View’ is not a valid JSX element.
The types returned by ‘render()’ are incompatible between these types.
Type ‘import(“/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index”).ReactNode’ is not assignable to type ‘React.ReactNode’.
Type ‘ReactElement<any, string | JSXElementConstructor>’ is not assignable to type ‘ReactNode’.
Property ‘children’ is missing in type ‘ReactElement<any, string | JSXElementConstructor>’ but required in type ‘ReactPortal’.
at makeError (/app/node_modules/execa/lib/error.js:60:11)
at handlePromise (/app/node_modules/execa/index.js:118:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
│ │
│ Project location: │
│ ./platformBuilds/standalone_web │

2 Likes

Hi Charles-

  1. I received the same error message when trying to build my webapp today (after no issues for the last 10+ builds)
  2. I have no fix but suspect if multiple people are receiving the same error then it is not anything we are doing?
1 Like

Hi Charles,

Same here!

1 Like

Same here :slightly_frowning_face:
Any idea if it’s something inside the app or it’s an error of appgyver?

Runtime version: 4.7.37;
AB version: 1.7.11
COMMAND:

FAILED with ERROR:

│ [ error ] [build] COMMAND:
npx next build
FAILED with ERROR:
Type error: ‘View’ cannot be used as a JSX component.
Its instance type ‘View’ is not a valid JSX element.
The types returned by ‘render()’ are incompatible between these types.
Type ‘import(“/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index”).ReactNode’ is not assignable to type ‘React.ReactNode’.
Type ‘ReactElement<any, string | JSXElementConstructor>’ is not assignable to type ‘ReactNode’.
Property ‘children’ is missing in type ‘ReactElement<any, string | JSXElementConstructor>’ but required in type ‘ReactPortal’.
Type error: ‘View’ cannot be used as a JSX component.
Its instance type ‘View’ is not a valid JSX element.
The types returned by ‘render()’ are incompatible between these types.
Type ‘import(“/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index”).ReactNode’ is not assignable to type ‘React.ReactNode’.
Type ‘ReactElement<any, string | JSXElementConstructor>’ is not assignable to type ‘ReactNode’.
Property ‘children’ is missing in type ‘ReactElement<any, string | JSXElementConstructor>’ but required in type ‘ReactPortal’.
Type error: ‘View’ cannot be used as a JSX component.
Its instance type ‘View’ is not a valid JSX element.
The types returned by ‘render()’ are incompatible between these types.
Type ‘import(“/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index”).ReactNode’ is not assignable to type ‘React.ReactNode’.
Type ‘ReactElement<any, string | JSXElementConstructor>’ is not assignable to type ‘ReactNode’.
Property ‘children’ is missing in type ‘ReactElement<any, string | JSXElementConstructor>’ but required in type ‘ReactPortal’.
Error: Command failed with exit code 1: npx next build
Failed to compile.
./src/components/App/AppSwitcher.tsx:10:6
Type error: ‘View’ cannot be used as a JSX component.
Its instance type ‘View’ is not a valid JSX element.
The types returned by ‘render()’ are incompatible between these types.
Type ‘import(“/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index”).ReactNode’ is not assignable to type ‘React.ReactNode’.
Type ‘ReactElement<any, string | JSXElementConstructor>’ is not assignable to type ‘ReactNode’.
Property ‘children’ is missing in type ‘ReactElement<any, string | JSXElementConstructor>’ but required in type ‘ReactPortal’.
at makeError (/app/node_modules/execa/lib/error.js:60:11)
at handlePromise (/app/node_modules/execa/index.js:118:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)

1 Like

I am getting the same issue as well.

1 Like

@Kirill_Leventcov ; it looks like the community edition appgyver build service is experiencing an outage.
However your status page does not reflect this at all. Thus the reason of this post so you can take necessary action and restore the build service.
Many thanks on behalf of the appgyver community.

PS.

Runtime version: 4.9.72; 
AB version: 1.7.11
COMMAND:

ASSETS_ARCHIVE_URL=https://appgyver-meap-assets.s3.amazonaws.com/bcss5138o87g1oqmcjds3bl8k6at?response-content-disposition=attachment%3B%20filename%3D%22assets.zip%22%3B%20filename%2A%3DUTF-8%27%27assets.zip&response-content-type=application%2Fzip&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJJSXXQRL4UNGBAXQ%2F20230918%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230918T220353Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=71b3fdb0a758e28ddec699a822ab0baa06e7cd056bee72801307b54128c556a3 NODE_OPTIONS=--max-old-space-size=10240  dockerrun --rm -v /home/ec2-user/builds/700360-web-298785:/app:z -v /home/ec2-user/.npmrc:/home/node/.npmrc  web ash -c 'NODE_OPTIONS="--max-old-space-size=10240" NEXT_SUPPORT_RELATIVE_PATHS=true ASSETS_ARCHIVE_URL="https://appgyver-meap-assets.s3.amazonaws.com/bcss5138o87g1oqmcjds3bl8k6at?response-content-disposition=attachment%3B%20filename%3D%22assets.zip%22%3B%20filename%2A%3DUTF-8%27%27assets.zip&response-content-type=application%2Fzip&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJJSXXQRL4UNGBAXQ%2F20230918%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230918T220353Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=71b3fdb0a758e28ddec699a822ab0baa06e7cd056bee72801307b54128c556a3" npx rnv export -p web -s standalone -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @appgyver/orchestra-template-standalone@4.9.72 -r'

FAILED with ERROR:

│ [ error ] [build] COMMAND:
npx next build
FAILED with ERROR:
Type error: 'View' cannot be used as a JSX component.
Its instance type 'View' is not a valid JSX element.
The types returned by 'render()' are incompatible between these types.
Type 'import("/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index").ReactNode' is not assignable to type 'React.ReactNode'.
Type 'ReactElement<any, string | JSXElementConstructor<any>>' is not assignable to type 'ReactNode'.
Property 'children' is missing in type 'ReactElement<any, string | JSXElementConstructor<any>>' but required in type 'ReactPortal'.
Type error: 'View' cannot be used as a JSX component.
Its instance type 'View' is not a valid JSX element.
The types returned by 'render()' are incompatible between these types.
Type 'import("/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index").ReactNode' is not assignable to type 'React.ReactNode'.
Type 'ReactElement<any, string | JSXElementConstructor<any>>' is not assignable to type 'ReactNode'.
Property 'children' is missing in type 'ReactElement<any, string | JSXElementConstructor<any>>' but required in type 'ReactPortal'.
Type error: 'View' cannot be used as a JSX component.
Its instance type 'View' is not a valid JSX element.
The types returned by 'render()' are incompatible between these types.
Type 'import("/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index").ReactNode' is not assignable to type 'React.ReactNode'.
Type 'ReactElement<any, string | JSXElementConstructor<any>>' is not assignable to type 'ReactNode'.
Property 'children' is missing in type 'ReactElement<any, string | JSXElementConstructor<any>>' but required in type 'ReactPortal'.
Error: Command failed with exit code 1: npx next build
Failed to compile.
./src/components/App/AppSwitcher.tsx:9:6
Type error: 'View' cannot be used as a JSX component.
Its instance type 'View' is not a valid JSX element.
The types returned by 'render()' are incompatible between these types.
Type 'import("/app/node_modules/@types/react-native/node_modules/@types/react/ts5.0/index").ReactNode' is not assignable to type 'React.ReactNode'.
Type 'ReactElement<any, string | JSXElementConstructor<any>>' is not assignable to type 'ReactNode'.
Property 'children' is missing in type 'ReactElement<any, string | JSXElementConstructor<any>>' but required in type 'ReactPortal'.
at makeError (/app/node_modules/execa/lib/error.js:60:11)
at handlePromise (/app/node_modules/execa/index.js:118:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
│ │
│ Project location: │
│ ./platformBuilds/standalone_web │

and the https://status.appgyver.com/ shows everything is green

1 Like

Same here. All was going well until yesterday. Even tried different runtimes but that didn’t help. Any light?

@Mari are there any issues you know of on Composure?

1 Like

Same here… HELP US ! :sweat_smile:

I opened a bug ticket : Type error: 'View' cannot be used as a JSX component. | Voters | AppGyver Community Edition

1 Like

Same thing here. So glad I’m not the only one; I feel like I’m going crazy.

1 Like

Hopefully Appgyver can give us an update soon. It’s disappointing that they haven’t already.

I have been having this problem too. I think the last time I was able to download it was about four days ago

4 days ago and Appgyver has not given any update on when it will be fixed?

I have the same problem, when will it be fixed?

1 Like

Any news? Same problem here. :melting_face:

1 Like

I’ve been waiting patiently because I figured Appgyver is working on it and would give us an update shortly. (I’ve been away for some time, and I forgot how unresponsive Appgyver can be.) I decided to keep building / making updates while I wait. Now, I’m stuck because I can’t test web, Android, or Apple.

I have Android and IOS builds that have also failed, and I’m fairly certain it is not me. Beginning of build fail messages below.

I really hope they fix this soon and have the professionalism to give us an update / eta on any fixes.

Apple
(My IOS distribution cert / p12 is valid & uploaded, so I’m fairly confident this is not me.)

Runtime version: 4.9.72;
AB version: 1.7.11
COMMAND:

ASSETS_ARCHIVE_URL=https://appgyver-meap-assets.s3.amazonaws.com/5fqvjehry0csqh9yrhk0bpt94fkp?response-content-disposition=attachment%3B%20filename%3D"assets.zip"%3B%20filename*%3DUTF-8’'assets.zip&response-content-type=application%2Fzip&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJJSXXQRL4UNGBAXQ%2F20230921%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230921T012300Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=fe844bdc6edbd41d86bfd402c1286723e62ed3ba3c99c6715292b2daa2542784 npxrnv export -p ios -s standalone_appstore -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @appgyver/orchestra-template-standalone@4.9.72 -r --xcodebuildArchiveArgs “OTHER_CODE_SIGN_FLAGS="–keychain\ AppGyver-312806"”

FAILED with ERROR:

│ [ error ] [export] COMMAND:
xcodebuildOTHER_CODE_SIGN_FLAGS=–keychain AppGyver-312806 -workspace /private/var/folders/jr/8x2sjv2d26d6wcx1dxmb_yqc0000gn/T/312806-ios-299149/platformBuilds/standalone_ios/RNVApp.xcworkspace -scheme RNVApp -sdk iphoneos -configuration Release archive -archivePath /private/var/folders/jr/8x2sjv2d26d6wcx1dxmb_yqc0000gn/T/312806-ios-299149/platformBuilds/standalone_ios/release/RNVApp.xcarchive
FAILED with ERROR:
/var/folders/jr/8x2sjv2d26d6wcx1dxmb_yqc0000gn/T/312806-ios-299149/platformBuilds/standalone_ios/RNVApp.xcodeproj: error: No signing certificate “iOS Distribution” found: No “iOS Distribution” signing certificate matching team ID “G9XUKQL6LU” with a private key was found. (in target ‘RNVApp’ from project ‘RNVApp’)

Android
(from what I can decipher I do not think this is anything I can fix)

Runtime version: 4.9.72;
AB version: 1.7.11
COMMAND:

ASSETS_ARCHIVE_URL=https://appgyver-meap-assets.s3.amazonaws.com/5fqvjehry0csqh9yrhk0bpt94fkp?response-content-disposition=attachment%3B%20filename%3D"assets.zip"%3B%20filename*%3DUTF-8''assets.zip&response-content-type=application%2Fzip&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJJSXXQRL4UNGBAXQ%2F20230921%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230921T012300Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=fe844bdc6edbd41d86bfd402c1286723e62ed3ba3c99c6715292b2daa2542784 NODE_OPTIONS=–max-old-space-size=10240 npxrnv export -p android -s standalone_bundle -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @appgyver/orchestra-template-standalone@4.9.72 -r

FAILED with ERROR:

FAILURE: Build failed with an exception.

  • What went wrong:
    A problem occurred configuring project ‘:react-native-v8’.

com.android.builder.errors.EvalIssueException: NDK at /opt/asdk/ndk/21.4.7075529 did not have a source.properties file

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

BUILD FAILED in 21s

@Mari @Kirill_Leventcov can someone give an update on the build failures. Was hesitant to retag again, but I’m unsure of any other way to contact Appgyver for support.

The last time there were significant widespread build errors was Jun 29 to Jul 6 2023 - hoping it won’t be as long for a solution this time - I’m staying positive and am confident the team is working to solve this - thanks to the AppGyver team for working on a solution