Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question]: Defining Runtime Version #1274

Open
m-scipione opened this issue Oct 23, 2024 · 11 comments
Open

[Question]: Defining Runtime Version #1274

m-scipione opened this issue Oct 23, 2024 · 11 comments
Labels
question Further information is requested

Comments

@m-scipione
Copy link

Question

When trying to deploy, I receive an error saying "the runtime version of the extension package is currently set to '14.0'. The runtime version must be set to '13.1' or earlier in the app.json file in order to install the extension package on this server.

I see the problem but am wondering if there is a place to define the runtime version as a setting in one of the config jsons in the repo.

@m-scipione m-scipione added the question Further information is requested label Oct 23, 2024
@jonaswre
Copy link
Contributor

I'm 90% sure the answer is no. This error happens for me when there is no runtime defined in the app.json.

I think keeping them in the app.json is also the correct place. Because you might actually want to keep that intentionally low for some of your apps.

@freddydk
Copy link
Contributor

@jonaswre is right, you cannot define a global runtime version - you need to define it in app.json.
I haven't seen this myself though - could you share your app.json and your AL-Go settings (both project and repo)

Thanks

@m-scipione
Copy link
Author

m-scipione commented Oct 28, 2024 via email

@freddydk
Copy link
Contributor

If you could share you app.json (and then please edit things in the GitHub UI) - answering on emails are terrible to read.

@m-scipione
Copy link
Author

Yes, I'll reply on the GitHub UI going forward.

Here is the app.json

@freddydk
Copy link
Contributor

You don't need the Base Application dependency - it was replaced by an indirect dependency property called "Application" some versions ago.

When you specify "Application": "24.0.0.0" - you have a dependency on Base Application, System Application and the Foundation app - version 24. If you need 24.5 - then change Application to 24.5-

@m-scipione
Copy link
Author

Thank you! I manually deleted the dependency from app.json and the build went through as expected.

Are you familiar with the Simple Object Designer extension to speed up some of the AL development work? This particular app I've been troubleshooting here was written by that extension. So while I was able to get the AL-Go functions working by deleting the dependencies that the Simple Object Designer included in the app.json, I would have to manually delete that dependency each time I commit new code.

Have you come across any other instances of users combining the Simple Object Designer with the AL-Go repo?

@freddydk
Copy link
Contributor

Pinged @hougaard offline and he will check whether this problem is fixed in the latest version or it needs attention.
Stay tuned

@hougaard
Copy link

Hi @m-scipione @freddydk

I have just verified that the Simple Object Designer (12.0.0.484 and later) produces app.json without the extra dependency specified for both the Legacy and the Microsoft compiler.

/Erik

@m-scipione
Copy link
Author

Many thanks for checking, I have SOD v12.0.0.477 installed so will update now!

@hougaard
Copy link

Awesome, please keep me updated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants