⚠️ Bugs & Issues v7.4.x ⚠️ #5642

67 Answer(s)

• 

  0

  lizhaofeng created one year ago

  In the process of generating CRUD pages with abpSuite, I encountered Error CS1737.

  abp suite 7.4.0-rc4

  

  

  Save Cancel
• 

  1

  rafael.gonzales created one year ago

  There is another issue in the generated EfCoreEntityRepository.cs class

  The issue corresponds to the **FindAsync **method inside the **EfCoreRepository ** class

  There seems to be a problem between the nullable-enabled project and the non-enabled nullable project (EntityFramework Project).
  One method returns a nullable type while the other expects a non-nullable return value.

  This is a critical error for the new version.

  3>EfCoreUbigeoRepository.cs(14,106): Error CS8613 : Nullability of reference types of the return type of "Task<Ubigeo> EfCoreRepository<DemoDbContext, Ubigeo>.FindAsync(Expression<Func<Ubigeo, bool>> predicate, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))" does not match member "Task<Ubigeo?> IRepository<Ubigeo>.FindAsync(Expression<Func<Ubigeo, bool>> predicate, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))" implemented implicitly.  
  3>EfCoreUbigeoRepository.cs(14,106): Error CS8613 : Nullability of reference types of the return type of "Task<Ubigeo> EfCoreRepository<DemoDbContext, Ubigeo, Guid>.FindAsync(Guid id, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))" does not match the implicitly implemented member "Task<Ubigeo?> IReadOnlyBasicRepository<Ubigeo, Guid>.FindAsync(Guid id, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))".  
  3>------- Finished building project: D.EntitemoyFrameworkCore. Succeeded: False. Errors: 2. Warnings: 0  
  

  The solution for this is the following.

  In **EfCoreRepository.cs **

  Replace this code:

  public async override Task<TEntity> FindAsync( 
      Expression<Func<TEntity, bool>> predicate, 
      bool includeDetails = true, 
      CancellationToken cancellationToken = default) 
  { 
      return includeDetails 
          ? await (await WithDetailsAsync()) 
              .Where(predicate) 
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken)) 
          : await (await GetDbSetAsync()) 
              .Where(predicate) 
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken)); 
  } 
   
  

  For this

  public async override Task<TEntity?> FindAsync( 
      Expression<Func<TEntity, bool>> predicate, 
      bool includeDetails = true, 
      CancellationToken cancellationToken = default) 
  { 
      return includeDetails 
          ? await (await WithDetailsAsync()) 
              .Where(predicate) 
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken)) 
          : await (await GetDbSetAsync()) 
              .Where(predicate) 
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken)); 
  } 
   
  

  And replace this code:

  public virtual async Task<TEntity> FindAsync(TKey id, bool includeDetails = true, CancellationToken cancellationToken = default) 
  { 
      return includeDetails 
          ? await (await WithDetailsAsync()).OrderBy(e => e.Id).FirstOrDefaultAsync(e => e.Id.Equals(id), GetCancellationToken(cancellationToken)) 
          : await (await GetDbSetAsync()).FindAsync(new object[] { id }, GetCancellationToken(cancellationToken)); 
  } 
   
  

  For this one public virtual async Task<TEntity?> FindAsync(TKey id, bool includeDetails = true, CancellationToken cancellationToken = default) { return includeDetails ? await (await WithDetailsAsync()).OrderBy(e => e.Id).FirstOrDefaultAsync(e => e.Id.Equals(id), GetCancellationToken(cancellationToken)) : await (await GetDbSetAsync()).FindAsync(new object[] { id }, GetCancellationToken(cancellationToken)); }

  Hi,

  Is there any news about this issue?

  Thanks!

  Save Cancel
• 

  0

  EngincanV created one year ago

  Support Team .NET Developer

  There is another issue in the generated EfCoreEntityRepository.cs class

  The issue corresponds to the **FindAsync **method inside the **EfCoreRepository ** class

  There seems to be a problem between the nullable-enabled project and the non-enabled nullable project (EntityFramework Project).
  One method returns a nullable type while the other expects a non-nullable return value.

  This is a critical error for the new version.

  3>EfCoreUbigeoRepository.cs(14,106): Error CS8613 : Nullability of reference types of the return type of "Task<Ubigeo> EfCoreRepository<DemoDbContext, Ubigeo>.FindAsync(Expression<Func<Ubigeo, bool>> predicate, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))" does not match member "Task<Ubigeo?> IRepository<Ubigeo>.FindAsync(Expression<Func<Ubigeo, bool>> predicate, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))" implemented implicitly.   
  3>EfCoreUbigeoRepository.cs(14,106): Error CS8613 : Nullability of reference types of the return type of "Task<Ubigeo> EfCoreRepository<DemoDbContext, Ubigeo, Guid>.FindAsync(Guid id, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))" does not match the implicitly implemented member "Task<Ubigeo?> IReadOnlyBasicRepository<Ubigeo, Guid>.FindAsync(Guid id, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))".   
  3>------- Finished building project: D.EntitemoyFrameworkCore. Succeeded: False. Errors: 2. Warnings: 0   
  

  The solution for this is the following.

  In **EfCoreRepository.cs **

  Replace this code:

  public async override Task<TEntity> FindAsync(  
      Expression<Func<TEntity, bool>> predicate,  
      bool includeDetails = true,  
      CancellationToken cancellationToken = default)  
  {  
      return includeDetails  
          ? await (await WithDetailsAsync())  
              .Where(predicate)  
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken))  
          : await (await GetDbSetAsync())  
              .Where(predicate)  
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken));  
  }  
    
  

  For this

  public async override Task<TEntity?> FindAsync(  
      Expression<Func<TEntity, bool>> predicate,  
      bool includeDetails = true,  
      CancellationToken cancellationToken = default)  
  {  
      return includeDetails  
          ? await (await WithDetailsAsync())  
              .Where(predicate)  
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken))  
          : await (await GetDbSetAsync())  
              .Where(predicate)  
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken));  
  }  
    
  

  And replace this code:

  public virtual async Task<TEntity> FindAsync(TKey id, bool includeDetails = true, CancellationToken cancellationToken = default)  
  {  
      return includeDetails  
          ? await (await WithDetailsAsync()).OrderBy(e => e.Id).FirstOrDefaultAsync(e => e.Id.Equals(id), GetCancellationToken(cancellationToken))  
          : await (await GetDbSetAsync()).FindAsync(new object[] { id }, GetCancellationToken(cancellationToken));  
  }  
    
  

  For this one
  public virtual async Task<TEntity?> FindAsync(TKey id, bool includeDetails = true, CancellationToken cancellationToken = default)
  {
  return includeDetails
  ? await (await WithDetailsAsync()).OrderBy(e => e.Id).FirstOrDefaultAsync(e => e.Id.Equals(id), GetCancellationToken(cancellationToken))
  : await (await GetDbSetAsync()).FindAsync(new object[] { id }, GetCancellationToken(cancellationToken));
  }

  Hi,

  Is there any news about this issue?

  Thanks!

  Hi Rafael, thanks for reporting. We have already fixed this (see https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.EntityFrameworkCore/Volo/Abp/Domain/Repositories/EntityFrameworkCore/EfCoreRepository.cs#L304) and enabled nullable annotations for all projects of both ABP Framework & ABP Commercial (https://github.com/abpframework/abp/issues/16610) and it will be available in v8.0.

  Save Cancel
• 

  0

  rafael.gonzales created one year ago

  There is another issue in the generated EfCoreEntityRepository.cs class

  The issue corresponds to the **FindAsync **method inside the **EfCoreRepository ** class

  There seems to be a problem between the nullable-enabled project and the non-enabled nullable project (EntityFramework Project).
  One method returns a nullable type while the other expects a non-nullable return value.

  This is a critical error for the new version.

  3>EfCoreUbigeoRepository.cs(14,106): Error CS8613 : Nullability of reference types of the return type of "Task<Ubigeo> EfCoreRepository<DemoDbContext, Ubigeo>.FindAsync(Expression<Func<Ubigeo, bool>> predicate, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))" does not match member "Task<Ubigeo?> IRepository<Ubigeo>.FindAsync(Expression<Func<Ubigeo, bool>> predicate, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))" implemented implicitly.    
  3>EfCoreUbigeoRepository.cs(14,106): Error CS8613 : Nullability of reference types of the return type of "Task<Ubigeo> EfCoreRepository<DemoDbContext, Ubigeo, Guid>.FindAsync(Guid id, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))" does not match the implicitly implemented member "Task<Ubigeo?> IReadOnlyBasicRepository<Ubigeo, Guid>.FindAsync(Guid id, bool includeDetails = true, CancellationToken cancellationToken = default(CancellationToken))".    
  3>------- Finished building project: D.EntitemoyFrameworkCore. Succeeded: False. Errors: 2. Warnings: 0    
  

  The solution for this is the following.

  In **EfCoreRepository.cs **

  Replace this code:

  public async override Task<TEntity> FindAsync(   
      Expression<Func<TEntity, bool>> predicate,   
      bool includeDetails = true,   
      CancellationToken cancellationToken = default)   
  {   
      return includeDetails   
          ? await (await WithDetailsAsync())   
              .Where(predicate)   
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken))   
          : await (await GetDbSetAsync())   
              .Where(predicate)   
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken));   
  }   
     
  

  For this

  public async override Task<TEntity?> FindAsync(   
      Expression<Func<TEntity, bool>> predicate,   
      bool includeDetails = true,   
      CancellationToken cancellationToken = default)   
  {   
      return includeDetails   
          ? await (await WithDetailsAsync())   
              .Where(predicate)   
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken))   
          : await (await GetDbSetAsync())   
              .Where(predicate)   
              .SingleOrDefaultAsync(GetCancellationToken(cancellationToken));   
  }   
     
  

  And replace this code:

  public virtual async Task<TEntity> FindAsync(TKey id, bool includeDetails = true, CancellationToken cancellationToken = default)   
  {   
      return includeDetails   
          ? await (await WithDetailsAsync()).OrderBy(e => e.Id).FirstOrDefaultAsync(e => e.Id.Equals(id), GetCancellationToken(cancellationToken))   
          : await (await GetDbSetAsync()).FindAsync(new object[] { id }, GetCancellationToken(cancellationToken));   
  }   
     
  

  For this one
  public virtual async Task<TEntity?> FindAsync(TKey id, bool includeDetails = true, CancellationToken cancellationToken = default)
  {
  return includeDetails
  ? await (await WithDetailsAsync()).OrderBy(e => e.Id).FirstOrDefaultAsync(e => e.Id.Equals(id), GetCancellationToken(cancellationToken))
  : await (await GetDbSetAsync()).FindAsync(new object[] { id }, GetCancellationToken(cancellationToken));
  }

  Hi,

  Is there any news about this issue?

  Thanks!

  Hi Rafael, thanks for reporting. We have already fixed this (see https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.EntityFrameworkCore/Volo/Abp/Domain/Repositories/EntityFrameworkCore/EfCoreRepository.cs#L304) and enabled nullable annotations for all projects of both ABP Framework & ABP Commercial (https://github.com/abpframework/abp/issues/16610) and it will be available in v8.0.

  Thanks for your answer!!

  Why is not that solution included in 7.4? In my opinion, the fix of EfCoreRepository, it's critical because it can lead to data issues right now. Is it possible to include at least the EfCoreRepository fix only or a temporary workaround?

  Save Cancel
• 

  0

  EngincanV created one year ago

  Support Team .NET Developer

  Why is not that solution included in 7.4? In my opinion, the fix of EfCoreRepository, it's critical because it can lead to data issues right now. Is it possible to include at least the EfCoreRepository fix only or a temporary workaround?

  We aimed to enable nullable annotations for all our projects in v8.0 (https://github.com/abpframework/abp/issues/16610), therefore we have made the related changes on the dev branch and because of that all of those changes will be included in v8.0 and unfortunately, it's not possible for us to include this change in the 7.4 release.

  Save Cancel
• 

  0

  Emanuele.Filardo created one year ago

  Hi, there is an issue in MAUI Android, ThemeManager doesnt change theme in dialog, you have to add the following line:

  public class ThemeManager : ISingletonDependency
  {
      private readonly IStorage _storage;
  
      public ThemeManager(IStorage storage)
      {
          _storage = storage;
      }
  
      public async Task<AppTheme> GetAppThemeAsync()
      {
          var storedTheme = await _storage.GetAsync(GeSAConsts.Settings.Theme);
  
          if (!storedTheme.IsNullOrEmpty())
          {
  #if ANDROID
              HandleAndroidDialogTheme();
  #endif
              return Enum.Parse<AppTheme>(storedTheme);
          }
  
          return AppTheme.Unspecified;
      }
  
      public async Task SetAppThemeAsync(AppTheme theme)
      {
          App.Current!.UserAppTheme = theme;
  
  #if ANDROID
          HandleAndroidDialogTheme();
  #endif
  
          await _storage.SetAsync(GeSAConsts.Settings.Theme, theme.ToString());
      }
  
      private static void HandleAndroidDialogTheme()
      {
          AndroidX.AppCompat.App.AppCompatDelegate.DefaultNightMode = App.Current!.UserAppTheme switch
          {
              AppTheme.Light => AndroidX.AppCompat.App.AppCompatDelegate.ModeNightNo,
              AppTheme.Dark => AndroidX.AppCompat.App.AppCompatDelegate.ModeNightYes,
              AppTheme.Unspecified => AndroidX.AppCompat.App.AppCompatDelegate.ModeNightFollowSystem,
              _ => AndroidX.AppCompat.App.AppCompatDelegate.ModeNightFollowSystem
          };
      }
  }
  

  HTH :-)

  Save Cancel
• 

  0

  ash.jackson created one year ago

  Suite fails when generating angular front-end in microservice solution

  Steps to produce:

  1. Create new microservice solution with abp new Test -t microservice-pro -u angular -csf
  2. Migrate databases and launch project
  3. Use suite to generate a new entity in the ProductService
  4. Observe suite produces a success message:
     1. 
  5. Re-load the angular UI
  6. Observe the permission for the new entity is created, but no UI has been added.

  I've reverted Cli and Suite to 7.3.3 and confirmed that this sequence works correctly in the previous version.

  This is the suite log output showing the error:

  2023-10-21 18:18:10.157 +01:00 [INF] 1/14 - EntityGenerateCommand started...
  2023-10-21 18:18:12.449 +01:00 [INF] 1/14 - EntityGenerateCommand completed.                           | Duration: 2287 ms.
  2023-10-21 18:18:12.449 +01:00 [INF] 2/14 - RepositoryCommand started...
  2023-10-21 18:18:12.583 +01:00 [INF] 2/14 - RepositoryCommand completed.                               | Duration: 134 ms.
  2023-10-21 18:18:12.583 +01:00 [INF] 3/14 - ManagerCommand started...
  2023-10-21 18:18:12.625 +01:00 [INF] 3/14 - ManagerCommand completed.                                  | Duration: 41 ms.
  2023-10-21 18:18:12.625 +01:00 [INF] 4/14 - AppServiceCommand started...
  2023-10-21 18:18:18.596 +01:00 [INF] 4/14 - AppServiceCommand completed.                               | Duration: 5970 ms.
  2023-10-21 18:18:18.596 +01:00 [INF] 5/14 - ProxyControllerCommand started...
  2023-10-21 18:18:18.627 +01:00 [INF] 5/14 - ProxyControllerCommand completed.                          | Duration: 31 ms.
  2023-10-21 18:18:18.627 +01:00 [INF] 6/14 - PermissionCommand started...
  2023-10-21 18:18:18.677 +01:00 [INF] 6/14 - PermissionCommand completed.                               | Duration: 49 ms.
  2023-10-21 18:18:18.677 +01:00 [INF] 7/14 - ApplicationObjectMappingCommand started...
  2023-10-21 18:18:18.692 +01:00 [INF] 7/14 - ApplicationObjectMappingCommand completed.                 | Duration: 14 ms.
  2023-10-21 18:18:18.692 +01:00 [INF] 8/14 - UnitTestCommandCommand started...
  2023-10-21 18:18:18.762 +01:00 [INF] 8/14 - UnitTestCommandCommand completed.                          | Duration: 70 ms.
  2023-10-21 18:18:18.762 +01:00 [INF] 9/14 - GenerateProxyCommand started...
  2023-10-21 18:18:18.814 +01:00 [INF] 9/14 - GenerateProxyCommand completed.                            | Duration: 52 ms.
  2023-10-21 18:18:18.815 +01:00 [INF] 10/14 - MvcUiGenerateCommand started...
  2023-10-21 18:18:19.016 +01:00 [INF] 10/14 - MvcUiGenerateCommand completed.                            | Duration: 201 ms.
  2023-10-21 18:18:19.016 +01:00 [INF] 11/14 - MvcObjectMappingCommand started...
  2023-10-21 18:18:19.035 +01:00 [INF] 11/14 - MvcObjectMappingCommand completed.                         | Duration: 19 ms.
  2023-10-21 18:18:19.035 +01:00 [INF] 12/14 - MvcMenuContributorCommand started...
  2023-10-21 18:18:19.101 +01:00 [INF] 12/14 - MvcMenuContributorCommand completed.                       | Duration: 65 ms.
  2023-10-21 18:18:19.101 +01:00 [INF] 13/14 - AngularUiGenerateWithSchematicsCommand started...
  2023-10-21 18:18:51.525 +01:00 [INF] Running the Angular Schematics command:
  node run-schematics.mjs '/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/.bin/ng' g '.suite/schematics/collection.json:entity' microservice-pro Test.ProductService '/Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json' '/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular' 
  2023-10-21 18:18:56.009 +01:00 [INF] Angular Schematics command failed.
  /Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/execa/lib/error.js:60
  		error = new Error(message);
  		        ^
  
  Error: Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Test.ProductService --source /Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json
  [Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.
      at makeError (/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/execa/lib/error.js:60:11)
      at handlePromise (/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/execa/index.js:118:26)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async file:///Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/run-schematics.mjs:6:20 {
    shortMessage: 'Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Test.ProductService --source /Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json',
    command: '.suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Test.ProductService --source /Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json',
    escapedCommand: '".suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" --template microservice-pro --target Test.ProductService --source "/Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json"',
    exitCode: 1,
    signal: undefined,
    signalDescription: undefined,
    stdout: '',
    stderr: '[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.',
    failed: true,
    timedOut: false,
    isCanceled: false,
    killed: false
  }
  
  Node.js v18.17.1
  
  2023-10-21 18:18:56.025 +01:00 [INF] 13/14 - AngularUiGenerateWithSchematicsCommand completed.          | Duration: 36923 ms.
  

  Save Cancel
• 

  0

  rafael.gonzales created one year ago

  Hello!

  There is an issue in the interface with the following structure

  public interface IDEMODbContext : IEfCoreDbContext

  

  The DbSet properties there shouldn't have the null forgiven because it's an interface. There is no template to customize it and even if you fix it, every time you generate it from Suite, a new line with the same error gets created.

  Save Cancel
• 

  0

  rafael.gonzales created one year ago

  There is also an issue in the file DEMOApplicationTests.cs

  

  There should be a null forgiven in every result.Property or we will be having compilation error. It happens because the result is a nullable variable.

  It happens in the following methods.

  • public async Task CreateAsync()
  • public async Task UpdateAsync()

  Save Cancel
• 

  0

  lizhaofeng created one year ago

  ABP Suite does not support generating CRUD pages for entities with GUID types.

  Only the Application template does not support it.

  

  Save Cancel
• 

  0

  Navneet@aol.com.au created one year ago

  Bug Report: IdentityClaimType Version: 7.4.1 App: MVC Application How to reproduce Bug:-

  1. Create a new ClaimType
  2. Assign ClaimType to Users and Roles
  3. Bug1: When you delete previously created and assigned ClaimTypes, it doesn't give any error that this claim is in use in User & Role.
  4. Bug 2: Deleting Claim Types, delete from AbpClaimTypes but it doesn't delete from AbpRoleClaims and AbpUserClaims.
  5. Bug 3: AbpRoleClaims and AbpUserClaims can only be deleted by deleting them from the backend DatabaseServer, not from UI

  . . . Is there any quickfix I can use in my production server?

  Save Cancel
• 

  0

  linhhn@arius.vn created one year ago

  In Angular UI 7.4.1, modal add/edit user When username contains non-alphabetic characters, the validate message is displaying incorrectly even though the server returns the correct error

  

  Save Cancel
• 

  0

  Emanuele.Filardo created one year ago

  if someone has startup issue with MAUI Mobile for Android see this

  Save Cancel
• 

  0

  464199480 created one year ago

  abp update ABP CLI 7.4.2 Cannot update Volo.* packages! An error occurred while updating the package "Volo.Abp.Core". Error: Object reference not set to an instance of an object. Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at Volo.Abp.Cli.ProjectModification.VoloNugetPackagesVersionUpdater.UpdateVoloPackagesAsync(String content, Boolean includeNightlyPreviews, Boolean includeReleaseCandidates, Boolean switchToStable, SemanticVersion latestNugetVersion, SemanticVersion latestNugetReleaseCandidateVersion, String latestMyGetVersion, String specifiedVersion) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectModification\VoloNugetPackagesVersionUpdater.cs:line 184 Volo packages are updated in Taitans.Abp.Commercial.Core project.

  Save Cancel
• 

  0

  rafael.gonzales created one year ago

  Hello, Can we have a "Bugs & Issues" thread for v8.0.0?

  Save Cancel
• 

  0

  EngincanV created one year ago

  Support Team .NET Developer

  Hello, Can we have a "Bugs & Issues" thread for v8.0.0?

  Hi, thanks for reminding. Here is the thread link: https://support.abp.io/QA/Questions/6260/Bugs--Issues-v80x

  Save Cancel
• 

  0

  iteabr2020 created one year ago

  Suite fails when generating angular front-end in microservice solution

  Steps to produce:

  1. Create new microservice solution with abp new Test -t microservice-pro -u angular -csf
  2. Migrate databases and launch project
  3. Use suite to generate a new entity in the ProductService
  4. Observe suite produces a success message:
     1. 
  5. Re-load the angular UI
  6. Observe the permission for the new entity is created, but no UI has been added.

  I've reverted Cli and Suite to 7.3.3 and confirmed that this sequence works correctly in the previous version.

  This is the suite log output showing the error:

  2023-10-21 18:18:10.157 +01:00 [INF] 1/14 - EntityGenerateCommand started... 
  2023-10-21 18:18:12.449 +01:00 [INF] 1/14 - EntityGenerateCommand completed.                           | Duration: 2287 ms. 
  2023-10-21 18:18:12.449 +01:00 [INF] 2/14 - RepositoryCommand started... 
  2023-10-21 18:18:12.583 +01:00 [INF] 2/14 - RepositoryCommand completed.                               | Duration: 134 ms. 
  2023-10-21 18:18:12.583 +01:00 [INF] 3/14 - ManagerCommand started... 
  2023-10-21 18:18:12.625 +01:00 [INF] 3/14 - ManagerCommand completed.                                  | Duration: 41 ms. 
  2023-10-21 18:18:12.625 +01:00 [INF] 4/14 - AppServiceCommand started... 
  2023-10-21 18:18:18.596 +01:00 [INF] 4/14 - AppServiceCommand completed.                               | Duration: 5970 ms. 
  2023-10-21 18:18:18.596 +01:00 [INF] 5/14 - ProxyControllerCommand started... 
  2023-10-21 18:18:18.627 +01:00 [INF] 5/14 - ProxyControllerCommand completed.                          | Duration: 31 ms. 
  2023-10-21 18:18:18.627 +01:00 [INF] 6/14 - PermissionCommand started... 
  2023-10-21 18:18:18.677 +01:00 [INF] 6/14 - PermissionCommand completed.                               | Duration: 49 ms. 
  2023-10-21 18:18:18.677 +01:00 [INF] 7/14 - ApplicationObjectMappingCommand started... 
  2023-10-21 18:18:18.692 +01:00 [INF] 7/14 - ApplicationObjectMappingCommand completed.                 | Duration: 14 ms. 
  2023-10-21 18:18:18.692 +01:00 [INF] 8/14 - UnitTestCommandCommand started... 
  2023-10-21 18:18:18.762 +01:00 [INF] 8/14 - UnitTestCommandCommand completed.                          | Duration: 70 ms. 
  2023-10-21 18:18:18.762 +01:00 [INF] 9/14 - GenerateProxyCommand started... 
  2023-10-21 18:18:18.814 +01:00 [INF] 9/14 - GenerateProxyCommand completed.                            | Duration: 52 ms. 
  2023-10-21 18:18:18.815 +01:00 [INF] 10/14 - MvcUiGenerateCommand started... 
  2023-10-21 18:18:19.016 +01:00 [INF] 10/14 - MvcUiGenerateCommand completed.                            | Duration: 201 ms. 
  2023-10-21 18:18:19.016 +01:00 [INF] 11/14 - MvcObjectMappingCommand started... 
  2023-10-21 18:18:19.035 +01:00 [INF] 11/14 - MvcObjectMappingCommand completed.                         | Duration: 19 ms. 
  2023-10-21 18:18:19.035 +01:00 [INF] 12/14 - MvcMenuContributorCommand started... 
  2023-10-21 18:18:19.101 +01:00 [INF] 12/14 - MvcMenuContributorCommand completed.                       | Duration: 65 ms. 
  2023-10-21 18:18:19.101 +01:00 [INF] 13/14 - AngularUiGenerateWithSchematicsCommand started... 
  2023-10-21 18:18:51.525 +01:00 [INF] Running the Angular Schematics command: 
  node run-schematics.mjs '/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/.bin/ng' g '.suite/schematics/collection.json:entity' microservice-pro Test.ProductService '/Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json' '/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular'  
  2023-10-21 18:18:56.009 +01:00 [INF] Angular Schematics command failed. 
  /Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/execa/lib/error.js:60 
    	error = new Error(message); 
    	        ^ 
   
  Error: Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Test.ProductService --source /Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json 
  [Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace. 
      at makeError (/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/execa/lib/error.js:60:11) 
      at handlePromise (/Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/node_modules/execa/index.js:118:26) 
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 
      at async file:///Users/ashjackson/Git/cloudbiz-so/Test/apps/angular/.suite/schematics/run-schematics.mjs:6:20 { 
    shortMessage: 'Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Test.ProductService --source /Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json', 
    command: '.suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template microservice-pro --target Test.ProductService --source /Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json', 
    escapedCommand: '".suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" --template microservice-pro --target Test.ProductService --source "/Users/ashjackson/Git/cloudbiz-so/Test/services/product/.suite/entities/Sku.json"', 
    exitCode: 1, 
    signal: undefined, 
    signalDescription: undefined, 
    stdout: '', 
    stderr: '[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.', 
    failed: true, 
    timedOut: false, 
    isCanceled: false, 
    killed: false 
  } 
   
  Node.js v18.17.1 
   
  2023-10-21 18:18:56.025 +01:00 [INF] 13/14 - AngularUiGenerateWithSchematicsCommand completed.          | Duration: 36923 ms. 
  

  any fixing on this?

  Save Cancel