Possibly unhandled rejection in Angular 1.6
This has been fixed with fix($q): Add traceback to unhandled promise rejections — Commit 316f60f and the fix is included in the v1.6.1 release.
angularjs-1.6
URL hash-bang (#!/) prefix instead of simple hash (#/) in Angular 1.6
It is new from AngularJS 1.6, which added a new hash prefix. Due to aa077e8, the default hash-prefix used for $location hash-bang URLs has changed from the empty string (”) to the bang (‘!’). If your application does not use HTML5 mode or is being run on browsers that do not support HTML5 mode, and … Read more
AngularJS All slashes in URL changed to %2F
%2F is the percent-encoding for the forward-slash / character. This problem is related to the fact that AngularJS 1.6 has changed the default for hash-bang urls in the $location service. To revert to the previous behavior: appModule.config([‘$locationProvider’, function($locationProvider) { $locationProvider.hashPrefix(”); }]); For more information, see SO: angularjs 1.6.0 (latest now) routes not working.
Why are AngularJS $http success/error methods deprecated? Removed from v1.6?
The problem was that .success and .error methods are not chainable because they ignore return values. This caused problems for people familiar with chaining and encouraged poor code from people unfamiliar with chaining. Witness all the examples on StackOverflow that use the deferred anti-pattern. To quote one of the AngularJS team: IMO .success and .error … Read more
Angular 1.6.0: “Possibly unhandled rejection” error [duplicate]
Try adding this code to your config. I had a similar issue once, and this workaround did the trick. app.config([‘$qProvider’, function ($qProvider) { $qProvider.errorOnUnhandledRejections(false); }]);
angularjs 1.6.0 (latest now) routes not working
Simply use hashbang #! in the href: <a href=”#!/add-quote”>Add Quote</a> Due to aa077e8, the default hash-prefix used for $location hash-bang URLs has changed from the empty string (”) to the bang (‘!’). If you actually want to have no hash-prefix, then you can restore the previous behavior by adding a configuration block to your application: … Read more