Angular generation fails while trying to generate new Entity + Localisation not compiling #10669

9 Answer(s)

• 

  0

  AI-Bot created 4 months ago

  Support Team ABP Agent

  • The schematics process is failing before it can generate anything because the --source file passed to the schematic is invalid JSON:
    • --source "L:/Projects/TVRS/.suite/entities/POI.json"
    • Error: Expected ',' or '}' after property value in JSON ... (line 14250 column 15)

  Fix

  1. Open this file and validate/repair it:
     • L:/Projects/TVRS/.suite/entities/POI.json
  2. Typical causes in Suite entity JSON:
     • trailing comma
     • unescaped quotes inside a string (e.g., " inside a display name/description)
     • copy/paste that introduced a control character
  3. After fixing JSON, re-run the entity UI generation in ABP Suite.

  Also check your Node.js version

  You are running Node.js v24.13.1. That’s a very new major version and may not be what the ABP Suite bundled Angular tooling was tested with. If the JSON is valid but you still hit issues, switch to an LTS Node version commonly used by Angular tooling (e.g., Node 20/22 LTS), then retry.

  (Primary issue from the log is still the invalid JSON in POI.json.)

  Links:

  • https://abp.io/docs/latest/framework/ui/angular/quick-start

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  haepeto created 4 months ago

  I don't see any problem with the POI.json file. How can I send it over for you to investigate?

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  AI-Bot created 4 months ago

  Support Team ABP Agent

  • Please don’t paste the whole file here if it contains any sensitive info.
  • The standard way to share Suite/Studio reproduction materials is to contact ABP support via the contact form and attach the file (or a minimal reproducible project / the single POI.json).

  Use this link (verified reachable):

  • https://abp.io/contact

  What to send:

  1. L:/Projects/TVRS/.suite/entities/POI.json (the exact file referenced in the log)
  2. The Suite log file that contains the failing schematics command
  3. (Optional but helpful) a zip of .suite folder and the angular/.suite folder if the issue reproduces only with certain schematics/templates.

  If you want to self-diagnose locally before sending:

  • Run a strict JSON parse on that file (this will point to the exact line/column):

  node -e "JSON.parse(require('fs').readFileSync('L:/Projects/TVRS/.suite/entities/POI.json','utf8')); console.log('OK')"
  

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  haepeto created 4 months ago

  The local self-diagnose shows OK as output, so that means that the POI.json file is fine. I also generated another entity, with the same result.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  sumeyye.kurtulus created 4 months ago

  Support Team Angular Expert

  Hello,

  Thank you for sharing the related files and folders. I reviewed them and generated the code on my end; however, I was unable to reproduce the issue you described. Because of this, I suspect there may be a version mismatch between your application and the installed Suite version.

  You can check your Suite version through ABP Studio as explained here: ABP Studio – Automatic Version Matching

  Please ensure that the ABP Suite version is set to 10.3.0 if your project is also using version 10.3.0.

  If the issue persists after verifying the versions, could you also share the .suite folder located under the angular directory?

  Thank you for your cooperation.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  haepeto created 4 months ago

  Actually, I was nudged into upgrading to 10.4, and that magically fixed things. At least, the Angular generation issue. So the .suite folder located under the angular directory has been changed by now, and I didn't keep the zip file, sorry. It might be interesting to get some "cleaning" instructions, on how to start over with the Schematics components. Where can I find it?

  I do have another issue however, that I thought to be related, but it turns out it doesn't .

  The app translations are not working anymore since the upgrade to 10.3. You can see the effect on https://dev.tvrs.thconsulting.be/, even when not logged in.

  

  I do have my json resources files available, and the build just works as before. On my development machine (and that of my co-workers) everything works just fine. But the build and deploy to azure doesn't work. PS: I have 4 languages: en, fr, nl and nl-be. How do I troubleshoot this, and what are the typical issues with it? I don't even know how the framework is actually providing the translation resources to the user interface. Are they compiled into the angular static files, or to they reside in the backend swagger api?

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  haepeto created 4 months ago

  When I call https://backend.dev.tvrs.thconsulting.be/api/abp/application-localization?CultureName=en&OnlyDynamics=false I see a lot of return, but nothing specific to my own solution tvrs, only standard ABP messages

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  sumeyye.kurtulus created 4 months ago

  Support Team Angular Expert

  Actually, I was nudged into upgrading to 10.4, and that magically fixed things. At least, the Angular generation issue. So the .suite folder located under the angular directory has been changed by now, and I didn't keep the zip file, sorry. It might be interesting to get some "cleaning" instructions, on how to start over with the Schematics components. Where can I find it?

  Thank you for your response. You can check the ABP Suite version through the ABP Studio tool by following this document: Automatic Version Matching

  To clear any potential Angular-side cache issues, you can delete the temporary .suite, node_modules, and yarn.lock files/folders. After that, reinstall the dependencies and run code generation again using the Suite tool. This process will automatically recreate a fresh .suite folder in the same location.

  I do have another issue however, that I thought to be related, but it turns out it doesn't .

  The app translations are not working anymore since the upgrade to 10.3. You can see the effect on https://dev.tvrs.thconsulting.be/, even when not logged in.

  After reviewing your deployed website, I noticed that the following request does not return the expected localization key-value pairs:

  api/abp/application-localization?CultureName=en&OnlyDynamics=false

  This indicates that localization may not be functioning correctly in the deployed environment. You can review the following resources for more detailed information:

  • ABP Localization Fundamentals
  • ABP Angular Localization

  When I call https://backend.dev.tvrs.thconsulting.be/api/abp/application-localization?CultureName=en&OnlyDynamics=false I see a lot of return, but nothing specific to my own solution tvrs, only standard ABP messages

  From this perspective, your custom translations should appear under the following scope:

  "TVRS": {
    "texts": {},
    "baseResources": ["AbpValidation","AbpUi"]
  },
  

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

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  haepeto created 4 months ago

  After carefully reviewing https://abp.io/docs/latest/framework/fundamentals/localization I had to make a few changes, repair a broken dependency, and also, maybe not necessary, but my resource files got capitalised first nodes, and json is case sensitive, so I thought i should fix it. And also in HttpApi.Host, appSettings: "Settings": { "Abp.Localization.DefaultLanguage": "en" }

  Finally it resumed to work.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel

  1