IFS Developer Studio - bugs

Static Code Analysis:

Validating CVertiflexResponse-Cust.entity

Implementation file exists without the corresponding Model file

​@InfFilipV Can you select a different target version and see ? 

cannot open Context menu in new Customized fragment file
 

​@InfFilipV  can you pls send a screenshot and the version of the tool

Right click do nothing, just error is logged in IDE log.
app version is present in IDE log
 

Product Version: IFS Developer Studio 18 (Build 26.1.1220 2026-08-12)

Java: 17.0.8; OpenJDK 64-Bit Server VM 17.0.8+7-LTS

Runtime: OpenJDK Runtime Environment 17.0.8+7-LTS

System: Windows 11 version 10.0 running on amd64; UTF-8; en_US (developer_studio)

reinstallation helped, but daily reinstall is not solution… (maybe you could add button to delete cache folder in error console? to simplify that process, sometimes it really helps)

​@hamalk 
Again there is a problem with staring local server using Docker :/

Product Version: IFS Developer Studio 18 (Build 26.1.1220 2026-08-12)

After setting up the project I try to start the server and I get:

WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get "https://ifscloud.jfrog.io/v2/": unknown: Token failed verification: parse
Docker credentials or container repository invalid!

using the same credentials in terminal:

What is wrong???

and why this section can be seen once in a lifetime when you are setting up new project?

It is impossible to change the password to container repository.

​@Jonas Feigl ​@hamalk  - could anyone have a look on that?

Hi, Is true that I did not use Docker for a while, but I never filled this and it worked with some DEV nonProd images.

Really not my area of expertise so not something I can help with.

Hi,

There is no need to fill this data for customization projects. For Core Projects this data is used, but not for customization projects. That these fields are showing when setting up a new Customization project is a defect.

For customizations the tokens are delivered through the application itself, but due to a recent rotation of credentials this stopped working.

Both these issues are corrected in the next release of the Developer Studio tool, 26R2-EA tool release, planned on October 15th.

/Andreas

 “Generate Code and Deploy only Packages” deploys everything...