OK, so I decided to uninstall the new CLI and instead install the "old" CLI and use that to create a new similar solution. And to my surprise, that still contained what appears to be full docker support, including Docker Compose and the necessary scripts to build images etc.
With ABP Studio still being in beta (which seem to be true beta in this case with the bugs to go along with it), this really creates some confusion as to what solution to actually use when you want to build something for real production with ABP (not just with regards to Docker).
ABP really need to comment on this...
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.
