Message on WebCore site. What to do next?

#1

I have the following message on my Webcore ‘A newer SmartApp version (v0.2.0fd.20171105) is available, please update and publish all the webCoRE SmartApps in the SmartThings IDE.’

What must I do exactly?

Thanks

#2

Go to the smartapps in the ide and update the 4 webCoRE pistons.
If you have defined the github repo for webCoRE click on update from repo and then selext webCoRE(master).
Check all 4 webCoRE apps.
Check publish at the bottom and then save.

#3

Question: does this update fix the DST and scheduling issues? My pistons are working, except those that are scheduled… those are currently dead.

I would be reluctant to risk the stuff that’s still working by updating, unless it’s clear the update fixes the above.

#4

Fixed my issues.

#5

I’ve updated webcore successfully in the past.

But… When I go to Update from repo: WebCoRE Master: nothing appears on the screen.
And in webcore, I’m still getting the alert that there is a newer version I should install.

What to do next??

#6

Have you published after you updated. i.e. check the publish button at the button when you updated?
What is the message exactly.

#7

Yes.

And the message that appears is:
A newer SmartApp version (v0.2.0fd.20171105) is available, please update and publish all the webCoRE SmartApps in the SmartThings IDE.

It is the same message that appeared prior to me attempting to update.

And when I go to look at what is published, I get the following:
public static String version() { return “v0.2.0ec.20170927” }

So I know it has not done anything.

#8

Ok, the files appeared in the repository and updated successfully.

Time to test.

#9

I get the message that there is a new version, but it does not show in the update from repro. Is there a way to get the code and manually upgrade?

#10

I am having the same issue. My app and the browser based dashboard are both referencing old versions, even after updating in the Repo. I am going to try copy and pasting the code to see if that makes any difference.

UPDATE: Manually copying and pasting the code did not help. Any suggestions out there? I am having time based probelms and want to rule out the version. I also noticed that when I create new pistons, they reference the latest UI version.

#11

Did you hard reload your browser?

#12

@SThinglou. Perhaps try using ctrl + F5.
I assume it’s the same on all browsers. Don’t know though.

#13

In Chrome is it kinda different.

Enter developer mode (F12).

Then click on the refresh button but don’t release until you get three options. One will be hard reload.