UIApplication.sharedApplication not available

Asked 11/12, 2015 at 13:56 Answered 5/6, 2021 at 7:33

Solved ios swift ios-app-extension ios9.1 xcode7.1

I'm trying to get a reference to my app delegate from a UIViewController but I keep getting an this error message:

'sharedApplication()' is unavailable: Use view controller based solutions where appropriate instead.

I've been reading all the articles dealing with this kind of message but my problem seems unrelated as I'm not using any third party framework. While a Today Extension is part of my app, the class in which the error occurs is totally unrelated. I even created a completely new class and keep getting the same error:

When I do the same thing in a playground it works fine. What am I missing?

Basaltware answered 11/12, 2015 at 13:56 Comment(10)

Is this in an app extension or a standard app? Does your app contain app extensions? – Supernova 11/12, 2015 at 14:3

The error occurs in the app itself. The app does have an extension but I'm trying to get the appDel from the app, not from the extension. All classes in which the error occurs have no obvious relation with the extension. – Basaltware 11/12, 2015 at 14:7

Check to make sure that the file giving the error hasn't been associated with the extension target by mistake - see #32610276 – Supernova 11/12, 2015 at 14:10

I did. Both the original file as well as the newly created test class are only associated with the main app but not with the extension. – Basaltware 11/12, 2015 at 14:12

Hmm. Well for some reason Xcode thinks that this class is associated with your app extension which is why it is giving this error. – Supernova 11/12, 2015 at 14:13

Yeah, don't know where else to check. Could it be in the Schema or Build Settings? Any hint is appreciated. – Basaltware 11/12, 2015 at 14:25

@MuhammadWaqasBhati: Please don't add noise like "Thanks" to questions. – Sensorimotor 11/12, 2015 at 14:27

Have you tried cleaning your project and/or restarting Xcode? Xcode sometimes gets a bit lost... – Submediant 11/12, 2015 at 14:39

Yes, I did. Same result. – Basaltware 11/12, 2015 at 14:50

Details understanding refer this link #32031571 – Feld 4/5, 2018 at 6:58

Problem solved. I've been to the Build Settings of my app again and stumbled over

Require Only AppExtension-Safe API

all set to YES. The default though is NO. When I set this to NO the error disappeared.

I sure don't remember ever touching or even knowing about this but luckily now it works.

Basaltware answered 11/12, 2015 at 15:37 Comment(7)

Error is removed but default share view is not present. – Memory 7/2, 2017 at 7:55

Works! Had the same problem with some cocoa pods. I had to change it for the respective target in the pod project to fix it. Took a while until I figured it out since I first tried to apply it only to my build targets. – Moneymaking 29/6, 2017 at 13:6

Hi i m having the same issue but it could not solve the issue even after applied to your solution – Outgroup 13/7, 2017 at 11:4

I have alredy a project i have an requirement to add an extention i follow the process as mention in other tutorial but i want a custom layout when some one want to share image using my app extention so when i use the class which i need to include when user tap for sharing contaims the appdelegate instance n i am having the above mention issue. Can you please give me some guild line to resolve the issue – Outgroup 13/7, 2017 at 11:8

The Apple store will probably reject your app if you have an app extension and set the requirement to No. – Olivette 25/7, 2018 at 7:42

In my case, I had to remove the view controller from sources list of the Extension target instead. The extension is supposed to have this flag to YES. But my file is not intended to be part of this target. – Jd 12/3, 2020 at 17:1

good job, you saved me, i added oneSignalNotificationServiceExtension and all pods generate this error – Bouton 25/12, 2020 at 7:27

I ran into the same error when I created and added a new target to my project (a Remote Service Notification target) and added the target definition incorrectly in my podfile.

I was following directions from a third party notification platform and they were unclear as to where to place the target definition. Initially, I added the target definition within my main target, much like the Tests target definition. This mistake led me to this error.

I ended up moving the remote service notification target definition outside of my main target to the bottom of my podfile and that resolved my problem.

Secretarial answered 19/8, 2019 at 23:15 Comment(1)

I have the same thing happen to me. The third party notification platform in question was OneSignal. – Elfrieda 12/12, 2019 at 18:15

In case anyone came through this error after 3 years from the question time. Make sure that the swift file target Membership doesn't include a Today Extension.

Beelzebub answered 23/2, 2019 at 18:53 Comment(0)

-2

In my case, I have not defined import Foundation in the file causing the error. silly and late but could help an absent-minded like me. Cheers.

Malchus answered 5/6, 2021 at 7:33 Comment(1)

Not true. You can see in OP's question that they are already importing UIKit, which itself imports Foundation. You don't need to manually import Foundation when you already import UIKit, and doing it anyway would not solve OP's issue because it's unrelated to Foundation. – Nauru 5/6, 2021 at 12:18

Recommended topics

Hot tags