-
Notifications
You must be signed in to change notification settings - Fork 4.4k
🐛 Bug Report: After upgrading from v1.3.4 to v1.3.5, on refresh, I get 404 not found on the console. #5623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Upvote+ From what I see the error could be here if (\substr_count($routeUrl, '/') !== \substr_count($url, '/')) {
continue;
} But when loading the P.s. Here are values for example: <?php
$url = 'https://cloud.appwrite.io/console/organization-someId';
$routeUrl = 'https://cloud.appwrite.io/console';
var_dump(substr_count($routeUrl, '/')); // 3
var_dump(substr_count($url, '/')); // 4 |
You're right. When applying for an SSL certificate, there is the same issue here |
The fix will be done today, thanks for opening this! |
even im facing the same issue while using the oauth |
It was fixed in version 1.3.6 https://github.com/appwrite/appwrite/releases/tag/1.3.6 |
even after upgrading, I'm getting the same 404 error for deeplink |
How to use the fixed version for flutter SDK? |
The fix is for the Appwrite server part. the flutter SDK stayed the same. |
I am getting the same error in flutter client side while using appwrite cloud. Only thing different for me is the version |
The real version on the cloud is |
Alright. Thanks for the update. |
Hi @usamashafiqs are you still facing this issue? We had a fix rolled out recently. |
👟 Reproduction steps
I get 404 not found on the console when I refresh the page.
👍 Expected behavior
The console should work fine after refreshing the page.
👎 Actual Behavior
It actually showed 404 not found after refreshing the page.
🎲 Appwrite version
Version 1.3.x
💻 Operating system
Linux
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: