SDK Update 60 -> 63/64: Error encountered. Aborting

Hi there,

I'm wondering if anyone tried to update to the latest SDK (63 or 64)?
The thing is that we are trying to update it from version 60.0.732-1.4.2-2 to version 63.0.741-1.4.2-2 or 64.0.744-1.4.2-2, however, the process interrupts on "Starting 'app-icons-android' with the error "Error encountered. Aborting!".

It happens when updating the app (./sdk init-native) as well as when generating a new one ($SUGAR_MOBILE_SDK_HOME/<version>/sdk/generate-app).

Homebrew and node are updated to the latest version
jdk-11.0.19

There is no further explanation in the logs, only "Error encountered. Aborting!".



Has anyone run into the same problem and maybe addressed it?

Thank you.

Parents
  •    could you please provide exact command that you are executing to generate an app?
    i am specifically interested if there are any params provided to generate-app script

    also

    please try to run:

    cd $SUGAR_MOBILE_SDK_HOME/64.0.744-1.4.2-2

    ./sdk/generate-app

    does it work for you?

  • Hi   ,

    As per the command to generate an app - there are no params.
    For the new app:
    $SUGAR_MOBILE_SDK_HOME/64.0.744-1.4.2-2/sdk/generate-app

    For the updating from the previous sdk version:
    cd mobileapp
    ./sdk init-native

    We tried to run the command you suggested, but unfortunately, the result is the same:

  • got it

    what are your current node version and java versions?

    are you on Linux os?

    also it would be helpful if you attached all terminal logs starting from ./generate-app invocation

  • node v21.1.0
    Homebrew 4.1.19
    yarn 1.22.19
    jdk-11.0.19

    Linux, yes (debian 12)

    Attaching logs:
    logs.txt

  • tried your command and it worked well for me 

    i am on Mac though
    i suggest following

    please try

    1. remove node_modules folder (rm -rf node_modules)

    2. switch to node v18.16.0 (this version will be used during generate-app script)

    3. yarn install to install modules under this node version

    4. completely remove folder with existing app (invocation)

    5. run generate-app again

    if it doesn't help i suggest trying the same with java version 18

  • Hi  ,

    Unfortunately, the result is the same. We tried the steps you described, then the same with Java v18, deployed the environment from scratch with the needed versions (rather than upgrade/downgrade them) - nothing workedFrowning2

    Are there any other options/tips we could try?

  • i suspect one of the new node modules that was introduces maybe incompatible with your environment

    let's confirm this

    1. please check sdk version 60 again on your current environment. does it work now?

    2. switch to v64 and rm -rf node_modules and do npm install. check logs , were all modules installed successfully?

    i suspect maybe issue related to linux? meanwhile we will check if we can improve logging of the problem on our side

  • Hi  ,

    Sorry for the delay - but no good news so far:

    1 - yes
    2 - no errors in logs related to node_modules, looks ok

    We tried Ubuntu, behavior was the sameFrowning2

    Some additional logging would be a great help in locating where the issue is.

  • I'll give you some tips how you can debug failing script on your machine

    1. after you have encountered this error you will have {yourapp} or {yourapp}/Sample folder created. from this folder copy 'config' folder to you sdk installation folder

    2. in your sdk install folder  you have a gulp task named 'app-icons-android' that seems to be failing. this is essentially a node process that you need to debug

    here is my VSCode run configuration to do this (this is an equivalent of './gulp app-icons-android' console command)

    {
    "name": "Run a gulp task",
    "type": "node",
    "request": "launch",
    "program": "${workspaceRoot}/node_modules/gulp/bin/gulp.js",
    "stopOnEntry": false,
    "args": ["app-icons-android"],
    "cwd": "${workspaceRoot}",
    // "runtimeArgs": [
    // "--nolazy"
    // ],
    "console": "internalConsole"
    },
    3. put a breakpoint into app-icons.mjs and from here you can debug your error
    i hope this helps!
Reply
  • I'll give you some tips how you can debug failing script on your machine

    1. after you have encountered this error you will have {yourapp} or {yourapp}/Sample folder created. from this folder copy 'config' folder to you sdk installation folder

    2. in your sdk install folder  you have a gulp task named 'app-icons-android' that seems to be failing. this is essentially a node process that you need to debug

    here is my VSCode run configuration to do this (this is an equivalent of './gulp app-icons-android' console command)

    {
    "name": "Run a gulp task",
    "type": "node",
    "request": "launch",
    "program": "${workspaceRoot}/node_modules/gulp/bin/gulp.js",
    "stopOnEntry": false,
    "args": ["app-icons-android"],
    "cwd": "${workspaceRoot}",
    // "runtimeArgs": [
    // "--nolazy"
    // ],
    "console": "internalConsole"
    },
    3. put a breakpoint into app-icons.mjs and from here you can debug your error
    i hope this helps!
Children
No Data