Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No Provider for DeepLinker!

See original GitHub issue

Hi, I am just trying to add a component (TopTabPage) in my page and expecting my instance to be truthy. Have someone got the same problem or/and know the solution?

FAILED TESTS:
  HomePage
    ✖ initialises
      Chrome 55.0.2883 (Mac OS X 10.11.6)
    Error: No provider for DeepLinker!
        at NoProviderError.BaseError [as constructor] (webpack:///~/@angular/core/src/facade/errors.js:24:0 <- src/test.ts:7948:34)
        at NoProviderError.AbstractProviderError [as constructor] (webpack:///~/@angular/core/src/di/reflective_errors.js:41:0 <- src/test.ts:52518:16)
        at new NoProviderError (webpack:///~/@angular/core/src/di/reflective_errors.js:72:0 <- src/test.ts:52549:16)
        at ReflectiveInjector_._throwOrNull (webpack:///~/@angular/core/src/di/reflective_injector.js:758:0 <- src/test.ts:97335:19)
        at ReflectiveInjector_._getByKeyDefault (webpack:///~/@angular/core/src/di/reflective_injector.js:786:0 <- src/test.ts:97363:25)
        at ReflectiveInjector_._getByKey (webpack:///~/@angular/core/src/di/reflective_injector.js:749:0 <- src/test.ts:97326:25)
        at ReflectiveInjector_.get (webpack:///~/@angular/core/src/di/reflective_injector.js:558:0 <- src/test.ts:97135:21)
        at TestBed.get (webpack:///~/@angular/core/bundles/core-testing.umd.js:814:0 <- src/test.ts:12226:67)
        at CompiledTemplate.proxyViewClass.AppView.injectorGet (webpack:///~/@angular/core/src/linker/view.js:109:0 <- src/test.ts:97877:45)
        at CompiledTemplate.proxyViewClass.DebugAppView.injectorGet (webpack:///~/@angular/core/src/linker/view.js:351:0 <- src/test.ts:98119:49)
    Error: Uncaught (in promise): Error: Error in ./TopTabPage class TopTabPage - inline template:0:0 caused by: No provider for DeepLinker!
        at resolvePromise (webpack:///~/zone.js/dist/zone.js:468:0 <- src/test.ts:118950:31)
        at resolvePromise (webpack:///~/zone.js/dist/zone.js:453:0 <- src/test.ts:118935:17)
        at webpack:///~/zone.js/dist/zone.js:502:0 <- src/test.ts:118984:17
        at ZoneDelegate.invokeTask (webpack:///~/zone.js/dist/zone.js:265:0 <- src/test.ts:118747:35)
        at ProxyZoneSpec.onInvokeTask (webpack:///~/zone.js/dist/proxy.js:103:0 <- src/test.ts:88858:39)
        at ZoneDelegate.invokeTask (webpack:///~/zone.js/dist/zone.js:264:0 <- src/test.ts:118746:40)
        at Zone.runTask (webpack:///~/zone.js/dist/zone.js:154:0 <- src/test.ts:118636:47)
        at drainMicroTaskQueue (webpack:///~/zone.js/dist/zone.js:401:0 <- src/test.ts:118883:35)
        at ZoneTask.invoke (webpack:///~/zone.js/dist/zone.js:339:0 <- src/test.ts:118821:25)
        at data.args.(anonymous function) (webpack:///~/zone.js/dist/zone.js:970:0 <- src/test.ts:119452:25)

Issue Analytics

State:
Created 7 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

lathonezcommented, Nov 28, 2017

Had this issue with a component using ion-select, the following worked:

        {provide: DeepLinker, useFactory: () => ConfigMock.instance()},

basically mock out the deep linker with something. MMV with tabs page

1reaction

lathonezcommented, Jan 21, 2017

Mocking was probably the way to go. From the limited details provided it looks like “DeepLinker” expects a parent variable with of type NavController (NavMock). I’ve not heard of DeepLinker and am AFK so can’t be sure.

As there is no issue with the repository I am going to close this issue, please see #191 for the suggested path for getting help with general unit testing problems.

Thanks

Top Results From Across the Web

Error: No provider for DeepLinker while unit testing components

I have not used DeepLinker anywhere in my app. I am thinking it might be a dependency of something in my providers. I...

Error: No provider for DeepLinker while unit testing components

Testing suite is still not ready in ionic 2. So I am using this tutorial for the test. This essentially uses angular 2...

Why I will no longer use deep linking from the ... - Droidcon

Why I will no longer use deep linking from the Navigation Component. Blog Infos ... <deepLink app:uri="company.com/customer/favorites" />.

Create Deep Links to App Content - Android Developers

Create Deep Links to App Content · On this page · Add intent filters for incoming links · Read data from incoming intents...

Why I will no longer use deep linking from ... - ProAndroidDev

Far from ideal, because you have to duplicate deepLink, it's easy to forget ... As a result, when opening the link https://company.com/user/subscriptions, ...