The build in updater support was added in 1.0.1.
The first thing I did was check that the built in update works and it does as long as you have the minimum version that supports in app updates (v1.0.1)
Just manually download from the store, going forward you should be good to go with in app updates.
Got it.
Thanks a lot.
@Norm is it possible to get rid of the fade-in cookie-policy button?
the picture shows what it looks like on desktop view.
On an iPhone SE the whole button is visible.
I am not seeing that here on desktop but it’s pretty annoying on mobile and remains, even after accepting the policy. This is on an Android.
Yeah, that’s what I mean.
May be Norm can change this.
I totally agree. But it needs to be overhauled.
Sure …
A option to remove that fade in cookie button ( if you want ) and change the text. Also and in Opt in / out option were perfect 
@Norm, I know there’re more important things to do e.g. Beta5 crash etc.
But this annoying fade-in button has got to go. It looks awful on mobile.
Please …
@Norm, I’m really begging you, please have a look at the cookie consent bric.
There should be a solution for the annoying fade-in button.
Me, as a non coder and probably many other people depend on that bric.
It functions well but that flag got to go, or make it selectable.
Hi @Bootsie
I totally agree. But why you dont use the code by:
It is really easy to use. If you need help, no problem … I try to help you
tom
Agree with your point, i have used the osano’s cookie consent, but the most relaible and user friendly is of seers that you can easily get from here
Maybe I’m wrong, but why don’t you just set …
revokable:false
… you’ll find the code in the footer of your exported html-files. And now if you click OK, the cookie hint disappears and no revoke button appears.
If you want the cookie hint to show again, just empty the cache or delete the saved website data.
Hi @Ghost
Does this work for version 4? And can you explain how I would alter it and place the code please?
@Fourier Sorry for the late reply.
I haven’t tested it right now, but the „Cookie consent Bric“ hasn’t changed in that regard and it should still work. You can change it from project to project in the exported HTML code, or change it permanently in the Bric’s HTML code.
In the exported HTML code, search for:
revokable:true,
and change it to:
revokable:false,
Or change it permanently in the Cookie Bric, you find it in the main menu >> Developer >> Bric Builder
revokable:true,
and change it to
revokable:false,
Save the changes to the Bric and you are good to go.
Hi Ghost,
Thanks so much. I actually found out also via one of the guys in here, Pete, I think. But this is great as it is also visual and helpful for not only me but possibly others who might get this problem.
Thanks Ghost.
It was @PeteSharp who showed me this to place between styles…
.cc-revoke {display: none;}
And that worked.
Can you please explain how and where to “place between styles”?
Thanks
OK, I got it, never mind, I put following in the Window/Code editor, under Project-Header:
<style>
.cc-revoke {display: none;}
</style>