Activities of "sumeyye.kurtulus"

Hello,

Thank you for explaining your problem by giving details. Since you have migrated from 8.3.4 to 9.3.4 , I need to remind you that we have made some set of adjustments on our side. The most important one is the standalone migration.

You can check details from here

1. 🔗 Migration guides
2. 🔗 9.3 Migration
3. 🔗 Standalone support

If you have also migrated your application to the new builder system, this could make a difference.

Thant is to say, the module and the token you have shared seem functional and not problematic. However, that would be the best if you could share

• how you have provided them
• the customizations you have done that could affect here

If you prefer, you could also share a minimal reproducible example via e-mail. Here is my address: sumeyye.kurtulus@volosoft.com

Thank you for your cooperation.

Hello again,

Thank you for giving extra details on your problem. It appears to be a builder registration mismatch problem and we will be releasing a fix for the next releases https://github.com/abpframework/abp/releases

You can change the localization registration for the time being until we publish the fix.

// app.config.ts
import { registerLocaleForEsBuild } from '@abp/ng.core/locale';
export const appConfig: ApplicationConfig = {
    provideAbpCore(
      withOptions({
        environment,
        registerLocaleFn: registerLocaleForEsBuild(),
      })
    ),
  ],
};

You can let us know if you need further assistance. Thank you for your cooperation.

Hello,

Thank you for providing extra details about your problem. I have tried the same approach on my side. However, I could not produce the same issue on my end. Here is how I have tried logging in as a tenant:

If you think that I have made a mistake while trying to produce the problem, you can guide me. You can also send a minimal, reproducible example to my e-mail address: sumeyye.kurtulus@volosoft.com

Thank you for your cooperation.

Hello again, Thank you for providing extra details about this problem. However, I could not produce the same problem on my end. That would be the best if you could send the project through e-mail. Here is my address: sumeyye.kurtulus@volosoft.com

Hello,

May I ask whether you have been using the standalone or module-based structure? We will also be updating the samples and tutorials.

You can let us know if you need further assistance. Thank you for your cooperation.

Hello, As you may notice from the template, the new Expo version has been applied, and the overall structure has been updated accordingly. We have also addressed the issues you mentioned. I recommend reviewing the latest documentation, which explains the updated structure in detail: 👉 https://abp.io/docs/10.0/framework/ui/react-native?Architecture=Tiered

If you encounter any other issues, I will be happy to assist further. Thank you for your cooperation.

We have included the latest implementations within the latest releases of ABP Studio. You can check the release notes here.

Thank you again for taking your time to send me a project. I have checked it and followed these steps:

1. Rollbacked to application builder system by running this command under apps > angular directory

2. Then added this missing configuration in angular.json

   {
     "projects": {
         "architect": {
           "build": {
             "options": {
               "browser": "projects/abp-solution3/src/main.ts",
             },
           },
         }
       },
     },
   }
   

3. I run this command under angular directory to add a library

   npx ng g @abp/ng.schematics:create-lib --package-name management-service --is-secondary-entrypoint false --template-type standalone --override true

Here are my related package versions

➜ ~ npm -v :: 10.9.2 ➜ ~ node -v :: v22.16.0 ➜ ~ yarn -v :: 1.22.22

I am also sending the project back that may help you go through:

https://drive.google.com/file/d/10kVEyn2JBxq1ojRnDvjfeJqpfjtp8UPW/view?usp=sharing

Thank you for checking both ways and responding.

I have used this command to test this issue, abp new AbpSolution1 -t microservice --ui-framework angular --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-language-management -file-management . However, both ways worked on my side. Did the library creation command failed again? Or, is that another issue occured while generating the entity?

If you prefer sending a minimal, reproducible example, I can also test it on my side. Here is my e-mail address: sumeyye.kurtulus@volosoft.com.

I can suggest you to delete temporary files under main angular directory that are node_modules, yarn.lock, .angular etc. and then reinstall the packages.

If this does not work, you can try keeping the application builder configurations and add the following property in angular.json:

{
  "projects": {
      "architect": {
        "build": {
          "options": {
            "browser": "projects/ticket9953/src/main.ts",
          },
        },
      }
    },
  },
}

Could I also get some information about the resolution date for this error? Since many of our projects are progressing on this structure, we don't want to experience problems in our projects.

I understand your urgency. However, I cannot provide an exact time for the next release as we plan them frequently. You can follow this link https://abp.io/docs/latest/studio/release-notes

I hope this workaround works. You can let us know if your need further guidance.