Hi, do you have web.config in your angular prod folder ? If yes can you please add a custom rule for getEnvConfig endpoint like below
<system.webServer> <rewrite> <rules> <rule name="Redirect" stopProcessing="true"> <match url="getEnvConfig" /> <action type="Redirect" url="dynamic-env.json" /> </rule> </rules> </rewrite> </system.webServer>
Why would there be a web.config in an Angular application?
Can confirm we are also seeing this problem but it seems like the source of it has been identified.
Still waiting for a reply here. Thanks.
have you checked the expo doc ? they said they have removed the support for 49 and 50 , they are only supporting sdk 51 on playstore, I manually tried to migrate all your existing code to 51 , since 49 is js
and 51 is typescript, its a significant rewrite.after converting your existing 180+ files manually to typscript , i got issue in inspecting the elements and localisation library
sdk 49 used ii18 js while i am trying to integrate i 118 next its not working ..
just have a look , I have also attached screenshot about expo dropped sdk 49 and 5o , in the starting of the conversation.
Agreed, SDK 51 and TypeScript should be the only option going forward with this, I see no value in "upgrading" to the out of support SDK 50 with only Javascript support.
Migrate react native to latest expo version with type script compatibility
Totally agree with this. I almost get the feeling that the React Native mobile project has been dropped in ABP in favor of MAUI, which would have been a logical decision if Microsoft ever got MAUI to be a serious alternative. Current state of MAUI is of course not ABPs fault but it leaves us in a situation where there really isn't a viable mobile option in ABP besides creating your own
After updating my project to 8.3.1 and 0.9.1 for ABP Studio, codemirror Error is popping up. My fix was to add the code mirror v5 files from codemirror's website to my main web app wwwroot/lib/codemirror folder. Then everything started working again. I must admit I am getting extremely frustrated going from a working project to one that completely fails everytime I update or add source code. It is costing many,many hours of development downtime trying to figure out what just broke? I like ABP and Studio, I would really like the product if I wasn't constantly beta testing everything.
I share your concerns about ABP Studio, it seems really promising but also like it is not quite there yet to use for stable production projects. Which creates a kind of weird situation with old stable CLI being phased out and ABP Suite being gimped so you can't create new projects with it.
What is the status of this now?
Microsoft.AspNetCore.Authorization.DefaultAuthorizationService: Information: Authorization failed. These requirements were not met:
PermissionRequirement: SettingManagement.Emailing
Microsoft.AspNetCore.Authorization.DefaultAuthorizationService: Information: Authorization failed. These requirements were not met:
PermissionRequirement: SettingManagement.TimeZone
Microsoft.AspNetCore.Authorization.DefaultAuthorizationService: Information: Authorization failed. These requirements were not met:
PermissionRequirement: AbpAccount.SettingManagement
Microsoft.AspNetCore.Authorization.DefaultAuthorizationService: Information: Authorization failed. These requirements were not met:
PermissionRequirement: AbpIdentity.SettingManagement
Microsoft.AspNetCore.Authorization.DefaultAuthorizationService: Information: Authorization failed. These requirements were not met:It's hard to understand this authentication problem, can I see your authserver configuration?
Considering that the last post was a year ago, I would imagine that they either have found a solution or given up by now :)
On Angular, mobile layout, the page scroll is preserved between pages where it should not :
Confirmed on https://demo.abp.io/ which I presume is the latest version
didn't understand the problem here. can you show the correct / expected behaviour?
I believe that what is meant is that when navigating to a new page, it should start from the top rather than at the scroll position of the previous page.
You mentioned that there are several disadvantages compared to the previous approach, but I would appreciate some clarification on this.
For instance, in the scenario where we didn’t use a mono-repo setup, you would move the Angular folder to a new repository. Has this process changed with the new template? Or do you find it more challenging to set up CI/CD pipelines with the new folder structure? What specific aspects are causing more difficulties compared to the old approach?
Please know that we thoroughly considered these factors during the design phase, as the new structure is a significant change for us. If there are substantial disadvantages, we are open to reconsidering the folder structure. However, most of the issues raised so far were already present in the previous setup.
While customizing the folder structure might seem like it breaks the 'intended workflow,' it doesn’t pose any issues for future updates or maintaining the template, as we're only changing the folder structure without affecting core functionalities.
In summary, both approaches have their pros and cons, but we opted for the current design based on the reasons I mentioned earlier.
Lastly, the ABP framework is inherently more aligned with a mono-repo setup. For example, the microservice solution leans towards this approach by default. However, if preferred, it's straightforward to work with multiple repositories. You can find more information here: https://abp.io/docs/latest/solution-templates/microservice/mono-repo-vs-multiple-repository-approaches.
Thanks for responding.
We've mostly used ABP for Blazor stuff before which more naturally is in the same repo as it is .NET so must admit that I have not given to much thought to the multi repo approach until now. But as we are currently doing an Angular ABP project, it pros and cons of a mono repo became more obvious. I am still on the fence here about that, as with regards to a mono repo, I can see both pros and cons. Which is what probably depends a lot on size of team, if you have dedicated people working with only parts of the application etc. From an ABP point of view I can understand how a mono repo could be beneficial, especially with regards to code generation etc.
With regards to CI/CD, it seems like seems like most "deployment tools" are made so that you have more dedicated repos, like when identifying what tech a certain repo have to automatically configure deployment, build paths etc. I am not really a DevOps expert myself so there might be a skill issue here, but at least it seem to require more manual configuration with everything in one repo.
When it comes to folder structure, I just can't come to terms with this new setup and it mixing folder like ".vs" and "etc" from the .NET solution with "angular" and "react native". It just feels wrong to me, and I would much rather having something more along the lines of the old structure. Now, you can of course argue how much of a problem this is, being that you would normally access the files using VS, VS Code etc which would mostly hide this unless you go poking around in the file system. On the other hand, as mentioned before, I can't really see any obvious advantages of this change, at least not to me as an ABP user, even though I can understand that there might be for you as ABP developers when building ABP Suite, Studio etc.
It would seem that if you want to create separate repos instead of a mono repo, for whatever reason, this new folder structure would make that a bit more challenging with one repo being in a subfolder of another etc. I would imagine that moving folders around to simply multi repos would probably break code generation etc. even though I have not tried this myself yet.
