Hi jerrys49113842
If I read this correctly, then your problem is not an unsatisfied bundle, but an unsatisfied service. If it so far that the SCR picked up your service, then your bundle must already be active.
With declarative services, I have seen similar behavior when a service with configuration-policy=require
is missing a configuration. Another possibility is that the activate
-method threw an exception.
Please verify it.
Thanks and Regards
Kautuk Sahni
Kautuk Sahni