7
App failing on all runtimes
in progress
B
Brenton Richards
APP ID: 321140
TYPE: Standalone
ERROR MESSAGE for runtimes 3.2.15, 3.3.5:
Unknown error, contact support for more details.
ERROR MESSAGE for runtimes 3.4.4, 3.4.5:
AB version: 0.2.64 {“stack”:“Error: Request failed with status code 403\n at createError (/usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/axios/lib/core/createError.js:16:15)\n at settle (/usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/axios/lib/core/settle.js:17:12)\n at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/axios/lib/adapters/http.js:269:11)\n at IncomingMessage.emit (events.js:412:35)\n at IncomingMessage.emit (domain.js:475:12)\n at endReadableNT (internal/streams/readable.js:1334:12)\n at processTicksAndRejections (internal/process/task_queues.js:82:21)”,“message”:“Request failed with status code 403”,“config”:{}}
Log In
Activity
Newest
Oldest
C
Codling Perfect
I'm facing similar issues while compiling/building for Android phones, all I had in my app was two buttons. Hopefully this will get fixed soon
E
Ender Maldonado
I'm stuck with this problem too, trying to compile on all versions. I even created an app without any content to test the build and it always gives the same error.
I am not using any special font, I use the one that appgyver gives you by default.

Kristian Gerkman
in progress
Kristian Gerkman
Hey Brenton Richards, checked your app, and it seems like the
Nunito
fonts upload has failed somehow - So removing that font should help you with building the app. If you're using that font in the app, you can just re-upload it with the same name, and it should work.Thanks,
Kristian
B
Brenton Richards
Kristian Gerkman: Thanks, Kristan. Is there a reason for this or did it just bug out? Don't want to be concerned about fonts in the future.
B
Brenton Richards
Kristian Gerkman: Hi. tried building again after removing the Nunito font entirely.
However, I am now getting "Unknown error" with builds 3.3.5 and below as well as the error below for builds 3.4.4 and above.
Runtime version: 3.4.4; AB version: 0.2.64 {"stack":"Error: Request failed with status code 403\n at createError (/usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/axios/lib/core/createError.js:16:15)\n at settle (/usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/axios/lib/core/settle.js:17:12)\n at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/axios/lib/adapters/http.js:269:11)\n at IncomingMessage.emit (events.js:412:35)\n at IncomingMessage.emit (domain.js:475:12)\n at endReadableNT (internal/streams/readable.js:1334:12)\n at processTicksAndRejections (internal/process/task_queues.js:82:21)","message":"Request failed with status code 403","config":{}}
B
Brenton Richards
Kristian Gerkman: Hi, any progress on this?
E
Ender Maldonado
Kristian Gerkman: I'm stuck with this problem too.
I am not using any special font, I use the one that appgyver gives you by default.