angular / angular

Deliver web apps with confidence 🚀
https://angular.dev
MIT License
95.73k stars 25.27k forks source link

The app does not work on iPad iOS9 #25503

Closed GTessarini closed 6 years ago

GTessarini commented 6 years ago

I have a web application built in Angular that always worked on desktop (Windows and Mac) and mobile (Android IOS). Updating my node version from 6.11.3 to 8.11.3 and intalling node modules related from this new version, the build of my application doesn`t load on iPad with the iOS 9 version. No script or style ir render, just a black page.

Here is my old package.json:

"dependencies": {
    "@angular/animations": "^5.1.0",
    "@angular/common": "^5.1.0",
    "@angular/compiler": "^5.1.0",
    "@angular/compiler-cli": "^5.1.0",
    "@angular/core": "^5.1.0",
    "@angular/forms": "^5.1.0",
    "@angular/http": "^5.1.0",
    "@angular/platform-browser": "^5.1.0",
    "@angular/platform-browser-dynamic": "^5.1.0",
    "@angular/platform-server": "^5.1.0",
    "@angular/router": "^5.1.0",
    "classlist.js": "^1.1.20150312",
    "core-js": "^2.4.1",
    "global-paths": "^1.0.0",
    "gsap": "^1.19.1",
    "hammerjs": "^2.0.8",
    "jquery": "^3.2.1",
    "ng-inline-svg": "^5.0.0",
    "rimraf": "^2.6.1",
    "rxjs": "^5.5.6",
    "zone.js": "^0.8.19"
  },
  "devDependencies": {
    "@angular/cli": "^1.6.4",
    "@angular/compiler-cli": "^5.1.0",
    "@angular/language-service": "^5.1.0",
    "@types/jasmine": "2.8.3",
    "@types/node": "~6.0.60",
    "autoprefixer": "^7.2.3",
    "circular-dependency-plugin": "^4.2.1",
    "codelyzer": "~4.0.1",
    "colors": "^1.1.2",
    "copy-webpack-plugin": "^4.1.1",
    "cross-env": "^5.1.4",
    "css-loader": "^0.28.1",
    "cssnano": "^3.10.0",
    "exports-loader": "^0.6.3",
    "file-loader": "^1.1.5",
    "fs-extra": "^4.0.1",
    "html-webpack-plugin": "^2.29.0",
    "ip": "^1.1.5",
    "istanbul-instrumenter-loader": "^3.0.0",
    "jasmine-core": "~2.6.2",
    "jasmine-spec-reporter": "~4.1.0",
    "karma": "~1.7.0",
    "karma-chrome-launcher": "~2.1.1",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "less-loader": "^4.0.5",
    "nodegit": "^0.20.1",
    "postcss-custom-properties": "^6.2.0",
    "postcss-import": "^11.0.0",
    "postcss-loader": "^2.0.10",
    "postcss-url": "^7.1.2",
    "protractor": "~5.1.2",
    "raw-loader": "^0.5.1",
    "sass-loader": "^6.0.3",
    "script-loader": "^0.7.0",
    "source-map-loader": "^0.2.0",
    "style-loader": "^0.13.1",
    "stylus-loader": "^3.0.1",
    "ts-node": "~3.2.0",
    "tslint": "~5.9.1",
    "typescript": "^2.5.3",
    "uglifyjs-webpack-plugin": "^1.1.5",
    "url-loader": "^0.6.2",
    "webpack": "~3.10.0",
    "webpack-concat-plugin": "1.4.0",
    "webpack-dev-server": "~2.9.3"
  }

Here is the changes on new package.json:

"jsdom": "^11.12.0",
    "sass": "^1.10.4",

    "copy-webpack-plugin": "^4.5.2",
    "nodegit": "^0.20.3",
    "webpack": "^3.10.0",
    "webpack-dev-server": "^2.9.7"

I`ve already tried modify the polyfill getting it from cdn and stopping of calling some custom scripts for my app, but the error persists.

skreborn commented 6 years ago

Please do provide a minimal reproduction of the problem. Simply "I have a web application" doesn't really help with the investigation. In any case, node version should make no difference whatsoever in runtime, as it is only used to build your project, so I think your problem lies elsewhere. Of course, it might be due to one of the packages you've upgraded along with node.

benlesh commented 6 years ago

I'm sorry but we don't understand the problem you are reporting.

If the problem still exists please open a new issue and provide a StackBlitz or repository reproducing the problem. You can use this StackBlitz template: https://stackblitz.com/fork/angular-gitter

angular-automatic-lock-bot[bot] commented 5 years ago

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.