Angular proxies error #9953

11 Answer(s)

• 

  0

  AI-Bot created 21 days ago

  Support Team ABP Agent

  • The issue where "Generating proxies" completes in 0 ms and no Angular proxy files are created for your new microservice (ManagementService) is typically caused by one of the following:

  1. The Angular project is not properly configured to recognize the new microservice for proxy generation.
  2. The ABP CLI is not targeting the correct Angular project or cannot resolve the backend API definition.
  3. The required configuration in angular.json, environment.ts, or tsconfig.base.json is missing or incorrect for the new service.

  Steps to Check and Resolve:

  1. Verify Angular Project Configuration:

     • Ensure your angular.json includes the correct projects and that the default project is set if you have multiple Angular projects.
     • Make sure the projects folder in your Angular solution contains the expected structure for each microservice UI.

  2. Check environment.ts:

     • In your Angular app's src/environments/environment.ts, ensure the apis section includes an entry for your new microservice, e.g.:

  apis: {
         default: {
           url: 'https://localhost:44300',
           rootNamespace: 'AbpSolution1'
         },
         managementService: {
           url: 'https://localhost:44301',
           rootNamespace: 'ManagementService'
         }
       }
  

  • The rootNamespace should match the backend namespace.

  3. Update tsconfig.base.json:
     • Add or update the proxy import paths:

  "paths": {
         "@proxy": ["src/app/proxy/index.ts"],
         "@proxy/*": ["src/app/proxy/*"]
       }
  

  4. Run Proxy Generation Manually:
     • Open a terminal in your Angular project root and run:

  abp generate-proxy -t ng
  

  • If you have multiple Angular projects, specify the project:

  abp generate-proxy -t ng --project <your-angular-project-name>
  

  • If prompted for backend module or API name, use the correct values (e.g., managementService).

  5. Check for Errors:

     • If the command completes instantly or with errors, check for missing or misconfigured @abp/ng.schematics package, or missing backend API endpoints.

  6. Restart Backend and Angular Apps:

     • Ensure all backend services are running and accessible before generating proxies.

  7. Review Documentation and Known Issues:

     • See the official docs and support threads for troubleshooting:
       • ABP Angular Service Proxies Documentation
       • Service Proxies Troubleshooting
       • Support Thread: Proxy Generation Issues
       • Support Thread: Proxy Generation Error

  If the above steps do not resolve the issue, double-check that your backend ManagementService exposes its API definition endpoint and that the Angular app can reach it.

  Sources:

  • ABP Angular Service Proxies Documentation
  • Service Proxies Troubleshooting
  • Support Thread: Proxy Generation Issues
  • Support Thread: Proxy Generation Error

  ---

  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.

  Save Cancel
• 

  0

  maliming created 20 days ago

  Support Team Fullstack Developer

  hi

  Could you please share the steps to reproduce the issue in a new template project?

  Thanks.

  Save Cancel
• 

  0

  yazilim.ithinka created 20 days ago

  Hello, of course.

  

  thanks

  Save Cancel
• 

  0

  maliming created 20 days ago

  Support Team Fullstack Developer

  Thanks. Our Suite team will check the Angular proxy issue.

  

  Save Cancel
• 

  0

  sumeyye.kurtulus created 19 days ago

  Support Team Angular Expert

  Hello,

  Thank you for reporting this problem. We will be fixing the related issue on the next patch release that you can follow the process through these links https://github.com/abpframework/abp/releases, https://abp.io/docs/latest/studio/release-notes

  I can temporarily suggest a rollback to the browser build system. For this, you need to update the related parts in your angular.json as follows: (you can also check this documentation that would be helpful https://angular.dev/tools/cli/build-system-migration)

  {
    ...
    "projects": {
      "ticket9953": {
        "projectType": "application",
        "schematics": {
          ...
        },
        "root": "projects/ticket9953",
        "sourceRoot": "projects/ticket9953/src",
        "prefix": "app",
        "architect": {
          "build": {
            "builder": "@angular-devkit/build-angular:browser",
            "options": {
              "outputPath": "dist/ticket9953",
              "index": "projects/ticket9953/src/index.html",
              "main": "projects/ticket9953/src/main.ts",
              "polyfills": "projects/ticket9953/src/polyfills.ts",
              ...
            },
            "configurations": {
              ...
              "development": {
                "buildOptimizer": false,
                "optimization": false,
                "vendorChunk": true,
                "extractLicenses": false,
                "sourceMap": true,
                "namedChunks": true
              }
            },
  					  ...
          },
          "serve": {
            "builder": "@angular-devkit/build-angular:dev-server",
            ...
          },
          "extract-i18n": {
            "builder": "@angular-devkit/build-angular:extract-i18n",
            ...
          },
          "test": {
            "builder": "@angular-devkit/build-angular:karma",
  	        ...
          },
        }
      },   
    },
  }
  
  

  You need to replace @angular/build with @angular-devkit/build-angular dependency in your package.json file.

  After reinstalling the packages in the root angular directory, you can create a library for your service using this command npx ng g @abp/ng.schematics:create-lib --package-name management-service --is-secondary-entrypoint false --template-type standalone --override true

  Then, you can use suite for creating more features.

  I am also processing a refund for your ticket. You can let us know if you need further assistance. Thank you for your cooperation.

  Save Cancel
• 

  0

  yazilim.ithinka created 19 days ago

  Hello, we have made the changes to angular.json and package.json as you requested.

  angular.json

  package.json

  Path "undefined" does not exist.

  We are receiving the message.

  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.

  Save Cancel
• 

  0

  sumeyye.kurtulus created 19 days ago

  Support Team Angular Expert

  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.

  Save Cancel
• 

  0

  yazilim.ithinka created 19 days ago

  Unfortunately, neither option worked. Do you have any other suggestions?

  Save Cancel
• 

  0

  sumeyye.kurtulus created 19 days ago

  Support Team Angular Expert

  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.

  Save Cancel
• 

  0

  yazilim.ithinka created 19 days ago

  I sent you the sample project. Could it be due to a missing application that should be installed on the computer or an incompatible version?

  Save Cancel
• 

  0

  sumeyye.kurtulus created 19 days ago

  Support Team Angular Expert

  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

  Save Cancel