So while using "themekit" in vs code terminal, I get the following message:
"This is the live theme on my-store. If you wish to make changes to it, then you will have to pass the --allow-live flag"
and to resolve it, I add --allow-live flag to the command and it works fine.(as described in the other answer on stack overflow)
BUT, while it did resolve the issue, everytime I try to use theme watch or theme deploy, it repeatedly asks me to use the --allow-live flag.
While researching themekit on google, youtube and other tutorials, I saw that it works fine for other developers even if they don't use --allow-live.
I read the following shopify documentation as well- https://www.shopify.com/partners/blog/checksums
How is "theme watch --allow-live" different from the "theme watch" command, and how do I make sure that everytime I use themekit, it doesn't ask me to add the flag. Is there a way by which it automatically allows live changes without manually adding the flag everytime I try using themekit.
The --allow-live is used only when you are working on a live theme.
If you don't want to use the --allow-live you must create a development theme and work on that, then the flag will not be required.
Please note that this flag was added recently (a few months back) so it's possible that you are reading older documentation where this flag was not present.
The flag cannot be stopped on a live theme, this is a prevention rule so that you don't overwrite the live theme without knowing that you are working on it.
So theme watch and theme watch --allow-live do the exactly same thing, but the second one just allows for the modification on the live theme.
Related
I'm trying to switch to Latex Workshop for VSCode, however I cannot get it to build after change.
I have it enabled in the settings, however it does not autobuild. After building manually the log says
Auto Build Run is temporarily disabled during a second.
at some point. I also made sure that Polling is active.
What is that supposed to mean and what is the fix?
I tried to set up Latex Workshop to autobuild, but it does not.
I think this is a bug. The way that I got auto build working was to enable autosave, because the "build on change" setting does seem to work and so the auto save triggers an auto build. Some instructions to enable autosave can be found e.g. in an answer here (in conjunction with the settings you mention).
Very new to Google Actions. Testing out tutorial stuff.
I have tried this in a couple of test projects just to double check. After initial run of any project I do not get any updates on draft projects. No changes show up in draft projects for me for both simulator and real device.
Started new project
Even blank project has basic conversation telling you where to add things next.
Change text.
Notice prompt does not change in testing environment.
In below pictures I have changed the words "hello world" with "Hey Dude" for both fulfillment and console output. I would expect Testing Prompt to respond with "Hey Dude from fulfillment and Hey Dude from the console!" But it does not. Instead it does not reflect any recent changes.
I think there may be two slightly different (but sometimes related) issues going on here.
The first is that there are known problems with the simulator being slow to pick up on updates, or them not seeming to show up. The second has to do with making sure you're deploying changes from the build-in code editor.
I don't have a clear answer to the first problem, although I know they're looking into it. I find that I can make some changes and they may not be noticed, but I know they have been picked up if I see the "Your preview is being updated..." spinner appear. There are other spinners that sometimes appear, but unless it explicitly says that it is being updated - the updates aren't always picked up. (Sometimes they are, however.)
Usually, if I don't see this, I'll go back and force an apparent change (delete a character from a webhook handler name, then add it back) and go back to the simulator. In general, this time it will say it is updating.
If you're using the Cloud Functions editor, you need to do three things:
Save the changes. You'll do this by clicking the "Save Fulfillment" button, but this only saves it so you can leave the editor. It doesn't mean that the simulator has access to it yet.
Deploy the changes. This deploys your code to Cloud Functions so they can be run. Note in the illustration that it says the code is saved, but not yet deployed.
Wait till the changes are fully deployed. Deploying takes time, and until it is completed, it won't be available in the simulator. While deploying, it lets you know.
Once it has deployed, however, the message changes, and you the impacts should be available through the simulator (although you may still need to see the "being updated" message to be sure).
Remember, however, that you don't need to use the "Cloud Functions editor" in order to deploy a webhook. You can deploy a webhook on any web server where
The host is public (so has a public IP address that Google can reach)
It can handle HTTPS with a non-self-signed certificate
You can even deploy yourself to Cloud Functions for Firebase, which is the same service that the Actions Builder uses. This way you have the URL set once in the Actions Builder and, once it is set, you won't need to change it.
But you'll still be able to change your code by managing your own deployment separate from Actions Builder.
I wanted to know the limitations of Visual editor in Optimizely? I am running a A/B test and wanted to make a few visual changes in my app. Can I make these changes when my app is live ?
The only limitation I could think of would be... it wont execute javascript for you.
And the order of execution that it would be executed last, after the custom JS/CSS.
Yes you can make changes when your website is live, so long as you don't publish it wont get reflected on your website. Utilize the preview mode to making as many changes as you want.
I am working on a project in VSCode, developing a React front-end application. Everything was working fine but I decided to clean up my code by using ESLint + Prettier + the AirBnb eslint guide.
I got this installed and of course, many issues came up. I started working through them, but these are causing the app to not compile. Ultimately, these are all code clean up issues, but now I can't get the app to run, and as i Make changes, I want to ensure I'm not breaking something else.
Does anyone know how to turn-off ESlinting in this situation so it will allow the app to turn?
Ultimately, it would be great if the issues appeared as simple "warnings" instead of "errors"...
I tried updating the .eslintrc.json file to change things to warn status, but it's not working.
There must be a simple way/toggle to enable/disable this checking? Or as I metioned, just have these appear as warnings for me to clean up?
I'm configuring Branch and seeing what I think is unexpected behavior upon trying to test my setup. I have an Ionic 3.7 app and am new to Ionic/iOS/Android development- so I've been following the Branch docs to try and get this configured (just for iOS right now).
What I've done so far:
I started with this guide: https://dev.branch.io/getting-started/sdk-integration-guide/guide/cordova/
The pre-requisite is that Universal Links are setup, which makes sense. In order to get that working, I clicking the link in the guide above, which took me to this guide: https://dev.branch.io/getting-started/universal-app-links/guide/cordova/
The Universal Link steps have gone fine until #3, where I'm trying to verify that my setup is correct. I created a Quick Link and texted it to my phone (which had a build of my app that I ran after adding the config in step 2).
Clicking the link starts to open the app (I see the splash screen), but it closes before loading is complete (I see a black screen momentarily). When I open this build of the app normally, it loads and runs normally
As I mentioned, I'm new to this- do I need to follow the Apple Universal Link setup (from here) with the apple-app-site-association file before starting the Branch config? I didn't see any mention of that in the guides I followed- however, it may be something so basic that it's assumed the user has done it already.
Regardless, I did configure that file and make it available as the Apple guide says. I'm still seeing the same behavior when I click my Branch link.
The 2nd Branch guide I posted only mentions that the app opens immediately without routing through Safari as a result of the test- is what I'm seeing actually correct? I don't have the SDK installed to handle the links, so I could see that being the case too.
UPDATE
I went ahead and installed the SDK, following the instructions here. It was somewhat confusing, as I wasn't sure if I should be supplementing the additions to config.xml from my step 1) above, or if my branch-config section should only have the keys from the SDK installation example.
I ended up commenting out the changes to config.xml from step 1) and it looks like it worked, as I now see the deeplink data when opening the app via the Quick Link I created before. I had previously added the domains to my entitlements file directly in Xcode before, though, so I'm now wondering if I need those extra config keys in order to persist the entitlements changes should I need to remove/readd the iOS platform.
Amruta from Branch.io here:
You can follow the iconic integration guide available on Github here.You need to update your config.xml with the Branch key assigned to your App, which can be found on the Account Settings page of the Branch dashboard. The URI scheme is the one you have defined in the Link Settings page of the Branch dashboard and the link domain for your Branch links is also defined on the Link Settings Page.
If you still have issues, I would recommend writing to integrations#branch.io.