Having an issue activating a theme using the fallback theme functionality. I've added @import "../twitter-bootstrap-sass/3.4.1-custom/assets/stylesheets/bootstrap/responsive-utilities"; to shopping.scss. Runs fine locally, deploys fine, but throws an error on activation: {"type":"error.SuiteScriptError","name":"51783","message":"The following file does not exist: .","id":null,"stack":["createError(N/error)"],"cause":{"message":"The following file does not exist: .","stack":["createError(N/error)","map(/SuiteBundles/Bundle 500777/ExtensionMechanism.Server/CompilersMapReduce/SassCompilerMapReduce.js:165)"],"name":"51783","data":{"response":null,"notifications":[]}},"notifyOff":false,"userFacing":true} I've done this successfully in another account using same theme tools version.....anyone know the issue?

did you check that this ("../twitter-bootstrap-sass/3.4.1-custom/assets/stylesheets/bootstrap/responsive-utilities") exist on your file cabinet ?

It's part of the base theme - I can see it in the extras folder and in the file cabinet. I have the correct version.

but did you went to the SuiteScripts/Deploy_Extensions folder and check that those files exists ?

yes - I think this is a limitation of using a fallback theme....I'm going back to a full theme customization

👀

@kkennedydesign Had the same issue after fixing the sass errors. I just keep activating the theme and eventually that error is not longer thrown and the activation gets completed.

I had no sass errors. The issue was when I added one @import for bootstrap responsive utilities to shopping css....it didn't like it. The odd thing is in another account it worked fine. We use these utilities all the time and I was tired of fighting ;>)

In that case, apart for the include you should add the file to the manifest,json of the theme

Not if you’re using a fallback theme

the filename was added to the manifest automatically. I know there are rules about added sass files and assets. I thought this would work for 2 reasons - first it worked in another account with a child theme, and second, the file exists in the bootstrap folder. I don't think it's a good strategy to have to keep activating and hoping it will complete, so we are moving back to the full theme. At some point I'll understand what the key differences are, but I am concerned I may have issues with the other account,

No I agree. Activating an extension should be deterministic and I can’t explain why the same files will/won’t activate … but I’d sure like to know

Has anyone filled out a support ticket for this? I'm experiencing the same issue.