Hello,

my app works fine on 4.7.11 but suddenly stopped being displayed on 4.7.12. Did you changed something in that extension?

I don't see any changes related to advertisements

Weird. I've added second extension with the same code as first and now it... works.

17 minutes ago, DawPi said:

Weird. I've added second extension with the same code as first and now it... works.

Probably it was removed somehow from the applications / appKey / data / extensions.json

On 7/18/2023 at 11:08 AM, Stuart Silvester said:

I don't see any changes related to advertisements

 

On 7/18/2023 at 11:31 AM, Adriano Faria said:

Probably it was removed somehow from the applications / appKey / data / extensions.json

Something weird there. I just had the same issue with an app. Someone reported:

I went to check and everything is ok but it kept claiming the Editor Location extension. So I went to check it in the extensions.json and it doesn't even exists:

So I removed the extension and recreated it with the same content and now the .json is there:

 

And I got no error in the app. It was working, according to the user, up to 4.7.10.

Leaving it here just in case you want to check it out.

Oh yes, make sure your apps have an extensions.json file, the legacy fallback code was removed in .12

Quote

• Removed legacy file loader for Extensions.

I'm going to assume they're old apps and you haven't added an extension since we moved to the JSON method (that's the action that writes the file)

In all apps? Removed from all apps?

1 minute ago, Adriano Faria said:

In all apps? Removed from all apps?

Extensions.json was introduced in 4.4, all apps that use extensions should have one.

Yes, this one should have as it was updated last time on March 13. I was expecting the extensions.json to be built when you export the app; it seems to be done only when you add/remove an extension.

Is that right?

Edited July 19, 20231 yr by Adriano Faria

1 hour ago, Stuart Silvester said:

I'm going to assume they're old apps and you haven't added an extension since we moved to the JSON method (that's the action that writes the file)

I guess you added this later. Ok, why didn’t you add this to a step upgrade to .12? 

🤷🏻‍♂️

Edited July 19, 20231 yr by Adriano Faria

Added what? extensions.json was implemented in 4.4, from the first beta in 2018.

There's nothing we can do in an upgrade step to fix a file missing from an application.

Yes, there is. Check if an app hasn’t the extension and then create it on a upgrade step. 

Videos (and a lot of other apps) added their extensions in 4.0 or 4.1. Seems a bit logical to me.

The code doesn't know whether that's a current extension or one that's there from an older version of the app that's no longer used (which is why we've opted to remove the legacy code, it was masking issues). In a lot of cases applications are stored in read-only locations, but as noted it's not something for us to generate on upgrade. I'll point out again, there has been 5 years to implement the proper extensions method.

42 minutes ago, Stuart Silvester said:

I'll point out again, there has been 5 years to implement the proper extensions method.

I’ll refrain from continuing this conversation. 👍

4 hours ago, Adriano Faria said:

I was expecting the extensions.json to be built when you export the app; it seems to be done only when you add/remove an extension.

I was sure that it works that way! If not then it's not logic at all. It should be generated when exporting... Why isn't? 🙂

Edited July 19, 20231 yr by DawPi

A suggestion, if I may. To enhance communication and avoid situations like that, it would be helpful to create a topic in Developer Connection every time a new version will break something.

For example:

Quote

Removed legacy file loader for Extensions.

At least to me, it isn't clear that will break all apps without extensions.json. It may be to others, but it isn't to me.

That would help the 3rd-party dev community to update their resources during the beta stage.

Thank you.