Skip to content

🐞 Bugs

A non-exhaustive list of encountered bugs and their solutions.

  1. When running npm run docs you get an error message including: docker: error during connect: This error may indicate that the docker daemon is not running.

    Solution: Simply start Docker.

  2. No 'Access-Control-Allow-Origin' header is present on the requested resource—when trying to get data from a REST API.

    Solution: Create a cors.json file:

    [
      {
        "origin": ["*"],
        "method": ["GET"],
        "maxAgeSeconds": 3600
      }
    ]
    
    and deploy the rules with:
    gsutil cors set cors.json gs://<your-cloud-storage-bucket>
    

  3. Error: PostCSS plugin autoprefixer requires PostCSS 8. Update PostCSS or downgrade this plugin.

    Solution: npm i postcss.

  4. Access to fetch at <pdf-url> from origin 'http://127.0.0.1:8000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

    Potential solution: https://stackoverflow.com/a/58153018/5021266

  5. [InsufficientPermissionError] after initializing Firebase in a production environment.

    Solution: Assign permissions in IAM console (see the installation guide).

  6. Firebase Hosting strip all cookies except for __session. Also see this issue.

    Solution: use __session cookie instead of session cookie. Also see Django cookies and headers. Furthermore, set the __session cookie as follows to ensure the cookie is passed in production.

    
    

  7. AppEngine warning - OpenBLAS WARNING - could not determine the L2 cache size on this system

  8. Firebase hosting deployment failing at hosting: uploading new files [5/128] with error Error: Task xyz failed: retries exhausted after 6 attempts.

    Solution: Delete the hidden folder in you project root directory .firebase/hosting.*.cache.

  9. When running npm run publish to create the container for Cloud Run, the program keeps retying, for example Retrying in 12 seconds.

    Solution: In this case, there is a container naming issue. Ensure gcloud run deploy APP-NAME matches the image tag gcr.io/PROJECT/APP-NAME.

  10. If you encounter a django-livereload-server NotImplementedError, then it is likely that you are using Python 3.8+ and need to add the following code to Lib\site-packages\tornado\platform\asyncio.py.

    import sys
    
    if sys.platform == 'win32':
        asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())
    

  11. HTTPError: 400 Client Error: File already exists. when publishing to PyPi

  12. Error: Can't Use Google Cloud Storage in Google Cloud Functions

    Solution - If you are using Firebase Storage in a Google Cloud Function, then you need to specify google-cloud-storage in your requirements.txt.

  13. Error: Firebase Hosting Base Rewrite Not Working

    Solution - In order to use a rewrite at the root in Firebase Hosting, you must not include an index.html file in the public folder.