Open evilthreads669966 opened 3 years ago
A performance costing workaround is @ApplicationContext
Nevermind. I think I tried to inject activity context into a singleton that isn't activity scoped
So since the updated HIlt. I need to take ReschedulerReceiver out of SingletonComponent but I haven't seen the code yet as it looks kike the newest version doesn't use ApplicationComponent any longer
It's complaining about ReschedulingReceiver matching the same key.