Hi all, it seems like ya are not read my comment well, I'll migrate to 51 but if you guys read the migration guid react expo recommend to update version incrementally. I'll migrate today to 51
https://reactnative.dev/docs/upgrading#expo-projects
Thanks,
MasumThanks for the clarification.
And it will be TypeScript as well then going forward?
@masum.ulu
Can you please confirm that Typescript will be used rather than Javascript going forward? Thanks
Hi again, I was working on this and other problems too, we'll release this enhancement for new template (Volo.Abp.Studio.Cli) we deprecated (Volo.Abp.Cli) dotnet tool's template. Development stage is done. Now it's on test stage. We'll release ASAP.
Can you please clarify what you (ABP) mean with the Volo.Abp.Cli being deprecated? AFAIK know, that is still the only template that has Docker support etc.
What is the status on this? ABP seem to have dropped support for Docker almost completely with the new CLI.
Pre-requirement check fails with 0.9.4
18:22:46.338 Information Failed task execution: "Checking pre-requirements" 18:22:46.338 Information ERROR: "An error has occured!" 18:22:46.338 Information ERROR DETAILS: "An internal error occurred during your request!" 18:22:46.339 Error Requested registry access is not allowed.
I have been testing this case for the version
8.3.x
However, logging in had no impact to duplicate the problem.
Also, thank you for sharing this question, but it should not be directly connected to this matter. If you are facing the same problem as in the question, that is discussable.
It seems like this happens when the browser window is 1200 px wide when the initial page load happens, this regardless of if you are logged in or not. Make browser window a bit narrower/wider and reload and the problem goes away, make it 1200 px and reload, and it will reappear. Please note that responsive mode in Dev Toolbar probably make things different and isn't something we have tried.
Stumbled upon this one by accident, not sure if it is actually related but interesting that it seems to affected by the exact same width of the browser window according to description
https://abp.io/support/questions/7937/POST-PUT-and-DELETE-requests-return-a-Bad-Request-400-error
I apologize for the delayed response. However, we have not been able to replicate the issue on our end. Please find a new record below for your reference.
Will give this a try again to see if things might have changed, what ABP version were you using? BTW, it seems like you tried this when not being logged in, which might change things as it changes the UI.
With the latest version of abp studio (0.9.1) I can't create a version of ABP 8.3.2.
It always creates version 8.3.1When will the new version of abp studio be released that supports the new abp release?
Can you find a solution so that when a new version of ABP is released, the version of abp studio that supports it will be released almost at the same time?
Thanks
It's happening since many versions before, ABP Studio never uses the latest version of ABP Framework while creating a project and it's a problem It doesn't get fixed and we don't have an answer from ABP Team of whether they have addressed it or not
We reverted to using old CLI + ABP suite instead, mostly as the code produced is also different. This is far from ideal for many reasons.