Trigger.io Reload - Configs missing - can't reload my live app - reload

I'm using Trigger.io Reload to send an update out for my app.
The problem is when I go to the 'Reload' tab in the Trigger Toolkit, the config for my live app is not listed.
I click 'Show configs' and Configs for the last 28 days are listed, but no further back than that. My last build that was released that I want to reload was about 38 days ago.
Also none of the configs that are listed show any active users.
Help! Where did the configs go and how do I get them back so I can update my users?
I'm wondering if this is related to the recent Toolkit update to support multiple developers and projects? Has anyone else had this issue?
Thanks

Related

Can not save transformation changes in Kentico Portal engine - errors in the console

I have a running Kentico 11 portal engine site and need to update the transformations in my navigation menu control. Something I have done many times before.
Today I went through all of the steps and the save button does not update the code. It never displays the change were saved messaging.
When I open the browser dev tools I see several errors on the page:
errors
A couple of things to check.
Is this happening in different browsers, also?
Can you save other transformations?
On this particular web part, if you select a different transformation, will that save successfully?
And, is the event log registering any errors?
Sounds like it may be a caching issue. What I'd suggest is the following:
restarting IIS
Open a private browser window and log in
attempt to make an edit to the code in question
If this does not resolve the issue, have you made any changes recently to the web.config, in particular the CMSHashstringsalt value? If so, this will cause your macros to become invalidated. You'll need to go to System > Macros > Signatures and check both boxes and resign the macros. It may take some time depending on your site but this could also help resolve your issue.

Deploying website to Azure: Each time requires cleaning the cached content to see the updated website [ASP.NET + REACT]

I am deploying my site to Azure from VS 2017. After each deployment, I am supposed to clean the cache of my browser to get the latest version of the website (or use ctrl+f5 to ignore the cached content when refreshing). But, this is a problem for the end users.
This is a asp.net + react website. So, the client-side code is cached in the browser. I have WEBSITE_DYNAMIC_CACHE set to 0, but did not help. Any suggestions? Is there a solution to this?
In VS 2017 right-click on the project and choose Publish. Click on Configure, then make sure the box is ticked for "remove additional files at destination"
I don't have enough votes to post screenshots yet, sorry!

Firebase database empty tab, rules load indefinitely

I just created a firebase project. And the database in the console appears empty. On previous projects, when you clicked on the empty white area, you were able to create database items by hand.
But clicking it doesn't do anything.
The rules tab is loading indefinitely, and i can't type anything.
I'm on Chrome last version, do you encounter such problems by creating new projects?
Here are some screenshots:
Ok, quick answer to my own question as i wasn't able, from my Angular2 App, to interact with database as well via websocket.
I'm working in a company with a (strong) proxy setup file. Disabled it on windows settings and all works now perfectly. Firebase website appears to rely on websockets.
Hope this information can be useful to someone else!

Reload module automatically became active without notice and cannot be removed

It's me again,
I just found out that Reload module became active and there is no way to turn it off. Its nowhere in module lists and so on. Is this some kind of new implementation, because it's not fair to enforce me using a module which I don't want to use.
Also I'm on 2nd type paid account and it costs me dearly for the services I get.
Please respond because I'm loosing precious time because of your fault.
Regards,
Ivan Popjelev
you can disable Reload by unchecking the core.general.reload checkbox in the App config section in your Toolkit.
Or, you can edit the config.json file to set reload: false if you prefer.
If you've migrated an app across from v1.4 to v2.0.0, we respect the Reload setting in the original app: we don't automatically enable Reload during the migration or anything like that.

Trigger.io: can I force a reload for all files and/or reset the reload history?

Let me explain a little bit:
I'm currently using a CDN to push reloads, due to some issues I've had with Trigger's reload infrastructure. For some reason, the latest reloads I'm pushing don't seem to be getting through to the app.
I don't 100% understand how the reloads work (I suspect they go by some kind of queue in the order you push reloads), but my suspicion is that it's because one of the reloads in the queue got overwritten or deleted from my CDN, so the .apk (it's an Android app) is looking for an update that no longer exists on the server, and isn't skipping ahead to future updates.
Anyway, the question is: can I wipe the slate clean somehow, so that the apps stop looking for that reload?
Or, is there a way to force all apps to get the latest pushed reload? I know the reloads only work with changed files, but is there a way to say "this is the latest official version" and force apps to reload to that one?
UPDATE: I think it might have something to do with the active configuration I'm pushing to. Is there any way to determine which config ID (i.e. the one that most users are using) in the Reload panel matches up to which reload or manifest file I have on my CDN, so I know which version those users are on?
First, a little background: when a device checks for a Reload update, it contacts the Trigger.io server to find out what the most recent applicable Reload update is, and where it is stored.
In your case, that will point the device towards a manifest file stored in your CDN, and the files referenced from it will be downloaded and swapped in.
So, the apps will automatically pick up the latest pushed Reload. If a Reload update is deleted or corrupted in the CDN, we still go back to the Trigger.io server so fixing the problem is just a case of re-pushing a newer Reload update.
There's no "out-of-the-box" way to connect which manifest files correspond to which config ID. One approach would be to install the app built from the relevant config ID, and let the Reload update occur. If you look at the debug log output as that Reload is happening, you can see what files are getting downloaded, and why.

Resources