sharedApplication is unavailable, not available on iOS (app extension). about gtm-session-fetcher HOT 12 CLOSED

@thomasvl OK. I added the GTM_BACKGROUND_TASK_FETCHING=0 in Preprocessor Macros for both release and debug. But I am still getting the error. Am I missing something. I updated pod file for my extension.

from gtm-session-fetcher.

I have the same issue as @georgek1991. Setting that value in the Preprocessor Macros doesn't appear to do anything.

from gtm-session-fetcher.

Alright, found the (a?) fix myself by combining information from this pull request and this comment...

In your Podfile, add the following lines:

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] = '$(inherited) GTM_BACKGROUND_UIAPPLICATION=0'
    end
  end
end

The preprocessing flag changed from GTM_BACKGROUND_TASK_FETCHING to GTM_BACKGROUND_UIAPPLICATION with that pull request (v1.1.8), so I figured I'd update here with a comment.

cc @paulofierro, if you didn’t find this already

from gtm-session-fetcher.

Just like the text you quoted, you'll want to define GTM_BACKGROUND_TASK_FETCHING=0 for your build.

from gtm-session-fetcher.

btw - I've tried to find a way to auto detect when the Xcode setting is enabled and auto enable the flag, but I haven't found a way yet.

from gtm-session-fetcher.

Thanks @thomasvl, I'll add it to build settings. There is similar issue with shareAppliation being used with other libraries (AFNetworking, epthread) as well.
ephread/Instructions#21
https://github.com/AFNetworking/AFNetworking/issues/2119

Could you please point me to the side-effects of not enabling background task fetching?

from gtm-session-fetcher.

Background task support doesn't really apply to extensions, it applies to apps.

For apps, if the user switches apps, it could cause the network request you fired off to get dropped because the OS doesn't let us know it was finished. By using a background task, we can help get the OS to call us back so we can let your code know the completion state of the request. So without it, there's a chance you'll have to issue the request again when the user returns to the app.

For extensions; it depends on what your are requesting. Dropping may be fine, or if it is acting on something (say a share extension), you likely want to coordinate things with your app so the extension could start it and hand off the operation to the app to ensure completion/etc.

from gtm-session-fetcher.

Hi @thomasvl

I have been dealing with other tasks at hand, sorry about posting a late reply. Adding a preprocessor task to declare "GTM_BACKGROUND_TASK_FETCHING=0" worked.

Thanks,

from gtm-session-fetcher.

where to declare GTM_BACKGROUND_TASK_FETCHING=0. can somebody point out.

from gtm-session-fetcher.

@georgek1991 in Xcode's Preprocessor Macros section.

from gtm-session-fetcher.

#74 includes a change that should make this a lot easy to deal with. There is still a directive to compile out the support, but things should work without having to do that.

We'll look at doing a CocoaPods bump also for this.

from gtm-session-fetcher.

1.1.9 pod pushed, so this should not need a define any more.

from gtm-session-fetcher.