Hello, we recently got the following bundles upgra...
# suitecommerce
v
Hello, we recently got the following bundles upgraded in our account: SuiteCommerce (2020.2.3) SuiteCommerce Extension Management (2020.2.0) SuiteCommerce Base Theme (2020.2.0) After this update, we modified our Custom Theme based on the newer Base Theme (2020.2.0) and deployed it. But, we're not able to activate our Custom Theme/Extensions since then. This is the error we get (during the "Impact Changes" step):
Copy code
{
  "type": "error.SuiteScriptError",
  "name": "431629",
  "message": "Hash.update: Missing a required argument: options.input",
  "stack": [
    "createError(N/error)"
  ],
  "cause": {
    "message": "Hash.update: Missing a required argument: options.input",
    "stack": [
      "createError(N/error)",
      "getMD5Hash(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/Services/FileApiSS2.js:338)",
      "(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/Services/FileApiSS2.js:283)",
      "E(/SuiteBundles/Bundle 343577/third_parties/underscore.js:6)",
      "copyFiles(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/Services/FileApiSS2.js:267)",
      "copyTmpFile(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/JobToProcess/ImpactChangesMapReduce.js:349)",
      "map(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/JobToProcess/ImpactChangesMapReduce.js:218)",
      "createError(N/error)"
    ],
    "name": "431629"
  },
  "id": "",
  "notifyOff": false,
  "userFacing": true
}
If we activate only the Base Theme, then the activation works. If we activate only our Custom Theme, or our Custom Theme and our extensions together, then the activation fails with the above error. The activation also fails with the same error when we try to activate the Base Theme with any of our extensions. Any idea why we must be getting this activation error?
f
Please check the tmp files generated. If there is any that is 0KB then the activation won´t work.
This is an example
v
Thanks for the response @Flo Meilan I do see entries like those in our manifest I'll get rid of them and try deploy-activation again
👍 1
This solution worked for us, Flo. We also found certain files with size 0 KB, other than the .tmp files, that we removed as well, after which the activations started working. Thanks again for your help. :)