@Saurabh many are experiencing this problem. This is not isolated.

How to fix this? My published delivery app in playstore shows 404. Hope there is a fix for this one... thanks

johnbedo works thank you

Indeed, it is important to go to domain.com first before going to domain.com/delivery

Strange situation

Its okay now in the browsers but the problem is with already published app in the playstore...

Its okay now in the browsers but the problem is with already published app in the playstore...

Same problem with my iOS and Android apps

this is a bug on the new 2.7.0 version because on the old version we not facing this issue. why we need to open the customer application URL first. it must work without open the customer URL first. I think foodomaa team need to check the issue and release the new update.

Its not working again... please fix urgently. Our delivery guys cannot perform their job now...

Any solution got regarding this issue?

Abiz009 Restore to 2.6.1 while waiting for the fix in 2.7.1 that's what I did personally

Thanks bro

my website isnt getting load. after updating it to v2.7
i successfully uploaded 'upload this file' to cpanel and extracted it shows error
my site isnt loading. if anyone can help

Not sure what is causing the issue. Because here is no change in the route or anything in the service worker that works with the route.

Weird part is it is working for some users without any issues. And working on some servers and some servers it's not.

On our testing hostinger it's working fine where as a new hostinger account it's not working.

So we are investigating this issue right now.

Unless I can recreate the issue on my local end, I cannot fix it. Trying...

PratikArora stick to the support portal please.

If you post it here, elaborate the issue with screenshot so that other user can understand.

"Not working" is very vague. But the screenshot you posted over support cleary states that the issue is with htaccess incompatibility or some server incompatibility.

Saurabh sure please try to resolve it asap

PejyArceCasem

Please provide your CPanel URL, username and password to the helpdesk (https://support.stackcanyon.com)

Found the issue and a fix.

Delete every code present in the .htaccess in the root directory to the folllowing:

FileETag none

<IfModule mod_rewrite.c>
    RewriteEngine On

    #Redirect to non-www with https
    RewriteCond %{HTTPS} off [OR]
    RewriteCond %{HTTP_HOST} ^www\. [NC]
    RewriteCond %{HTTP_HOST} ^(?:www\.)?(.+)$ [NC]
    RewriteRule ^ https://%1%{REQUEST_URI} [L,NE,R=301]
    
    RewriteBase /
    RewriteRule ^index\.html$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.html [L]
 </IfModule>


<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews -Indexes
    </IfModule>

    RewriteEngine On

    # Handle Authorization Header
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} (.+)/$
    RewriteRule ^ %1 [L,R=301]

    # Handle Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

# BEGIN Caching
<ifModule mod_headers.c>
<filesMatch "\\.(ico|pdf|flv|jpg|jpeg|png|gif|swf|ttf|otf|woff|woff2|eot|svg)$">
Header set Cache-Control "max-age=2592000, public"
</filesMatch>
<filesMatch "\\.(css)$">
Header set Cache-Control "max-age=2592000, public"
</filesMatch>
#<filesMatch "\\.(js)$">
#Header set Cache-Control "max-age=2592000, private"
#</filesMatch>
<filesMatch "\\.(xml|txt)$">
Header set Cache-Control "max-age=2592000, public, must-revalidate"
</filesMatch>
<filesMatch "\\.(html|html|php)$">
Header set Cache-Control "no-store"
</filesMatch>
</ifModule>
# END Caching

<FilesMatch ".(eot|otf|ttf|woff|woff2)">
    Header always set Access-Control-Allow-Origin "*"
</FilesMatch>

<Files .json>
    Header unset Cache-Control
</Files>

<Files .env>
order allow,deny
Deny from all
</Files>

Save the file and reload your /delivery route on chrome.
It should be working now.

IMPORTANT: DO NOT change the .htaccess file present in the "/public" directory.

===

I will be updating the same to v2.7.1 soon.

Saurabh Thank you so much for quick help