Getting DefaultSlingScript: No use provider could resolve identifier Issue on Production | Community
Skip to main content
touseefk2181136
touseefk2181136
February 23, 2023
Solved

Getting DefaultSlingScript: No use provider could resolve identifier Issue on Production

  • February 23, 2023
  • 1 reply
  • 779 views

I am getting following error on a page for a component on production but same component work fine on our QA environment. 

 

 

can it be due to some model class not being part of the package of something else ? I have been stuck with this issue for a long time.

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by nitesh_kumar-1

Hi @touseefk2181136 ,

 

The error you have posted is too generic.

 

You need to check logs to find what could be causing it, possible reasons could be

1.) Your bundle is not active, or the sling model is not deployed (check your bundle status)

2.) Some mandatory injection of some services/classes in the model is not satisfied which is causing it not to be initialized in the first place (you can find more details in error logs).

 

Check if there are relevant errors in the logs, you can add some excerpts here for better answers?

 

Hope this helps!

 

Regards,

Nitesh

1 reply

nitesh_kumar-1
Adobe Employee
nitesh_kumar-1Adobe EmployeeAccepted solution
Adobe Employee
February 23, 2023

Hi @touseefk2181136 ,

 

The error you have posted is too generic.

 

You need to check logs to find what could be causing it, possible reasons could be

1.) Your bundle is not active, or the sling model is not deployed (check your bundle status)

2.) Some mandatory injection of some services/classes in the model is not satisfied which is causing it not to be initialized in the first place (you can find more details in error logs).

 

Check if there are relevant errors in the logs, you can add some excerpts here for better answers?

 

Hope this helps!

 

Regards,

Nitesh

    Terms & ConditionsAccessibility statement

    Loading footer...