clang: error: linker command failed with exit code 1 (Cocoapods issue) #42
Labels
Comments
|
I did a flutter clean and attached the full output's from 2 build -- no difference -- just kept running the same command over and over .. generally the list of unresolved libraries goes down .. but not in this case .. This ALL has to do with timing .. we "somehow" need to make Run AFTER all the other pub spec dependencies so the other libraries that Flutter generates in the LD command are actually there ... |
|
@sjmcdowall the extension service does not need those other frameworks. The only external lib it needs is OneSignal. It should not even try to link to other Flutter libs. That is what we will want to be debugging. Are you sure your Podfile is still the one you posted earlier? If so, this is really bizarre, Cocoapods is trying to add the wrong frameworks to the Extension service that your own Podfile says should only link to OneSignal |
|
I totally understand that -- but this is how Flutter works -- its part of the project build file(s) it creates ... See the full verbose output I attached to the Issue on github ..
I have also posted in Flutter too about this ... but no response ...
And yes -- my Podfile is exactly the one posted .. here it is again .. as well as the Podfile.lock
I have no ideas on how to "fix" anything so the LD for OneSignal doesn't include the rest of the libraries... was hoping you guys had some idea .. this doesn't appear to be a "normal" Flutter dependency ... the Google FCM plugin doesn't need this stuff ...
…-- Podfile
# Uncomment this line to define a global platform for your project
platform :ios, '10.0'
# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'
def parse_KV_file(file, separator='=')
file_abs_path = File.expand_path(file)
if !File.exists? file_abs_path
return [];
end
pods_ary = []
skip_line_start_symbols = ["#", "/"]
File.foreach(file_abs_path) { |line|
next if skip_line_start_symbols.any? { |symbol| line =~ /^\s*#{symbol}/ }
plugin = line.split(pattern=separator)
if plugin.length == 2
podname = plugin[0].strip()
path = plugin[1].strip()
podpath = File.expand_path("#{path}", file_abs_path)
pods_ary.push({:name => podname, :path => podpath});
else
puts "Invalid plugin specification: #{line}"
end
}
return pods_ary
end
target 'Runner' do
# SJM -- For Swift plugins
# use_frameworks!
# Prepare symlinks folder. We use symlinks to avoid having Podfile.lock
# referring to absolute paths on developers' machines.
system('rm -rf .symlinks')
system('mkdir -p .symlinks/plugins')
# Flutter Pods
generated_xcode_build_settings = parse_KV_file('./Flutter/Generated.xcconfig')
if generated_xcode_build_settings.empty?
puts "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter packages get is executed first."
end
generated_xcode_build_settings.map { |p|
if p[:name] == 'FLUTTER_FRAMEWORK_DIR'
symlink = File.join('.symlinks', 'flutter')
File.symlink(File.dirname(p[:path]), symlink)
pod 'Flutter', :path => File.join(symlink, File.basename(p[:path]))
end
}
# Plugin Pods
plugin_pods = parse_KV_file('../.flutter-plugins')
plugin_pods.map { |p|
symlink = File.join('.symlinks', 'plugins', p[:name])
File.symlink(p[:path], symlink)
pod p[:name], :path => File.join(symlink, 'ios')
}
end
target 'OneSignalNotificationServiceExtension' do
pod 'OneSignal', '>= 2.9.3', '< 3.0'
end
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['SWIFT_VERSION'] = '4.0'
config.build_settings['ENABLE_BITCODE'] = 'NO'
end
end
end
-- Also -- here is the Podfile.lock that is generated (almost) each build..
PODS:
- device_info (0.0.1):
- Flutter
- Flutter (1.0.0)
- flutter_secure_storage (3.1.1):
- Flutter
- local_auth (0.0.1):
- Flutter
- location (0.0.1):
- Flutter
- onesignal (1.0.2):
- Flutter
- OneSignal (< 3.0, >= 2.9.3)
- OneSignal (2.9.3)
- open_file (0.0.1):
- Flutter
- package_info (0.0.1):
- Flutter
- path_provider (0.0.1):
- Flutter
- shared_preferences (0.0.1):
- Flutter
- uni_links (0.0.1):
- Flutter
- url_launcher (0.0.1):
- Flutter
DEPENDENCIES:
- device_info (from `.symlinks/plugins/device_info/ios`)
- Flutter (from `.symlinks/flutter/ios`)
- flutter_secure_storage (from `.symlinks/plugins/flutter_secure_storage/ios`)
- local_auth (from `.symlinks/plugins/local_auth/ios`)
- location (from `.symlinks/plugins/location/ios`)
- OneSignal (< 3.0, >= 2.9.3)
- onesignal (from `.symlinks/plugins/onesignal/ios`)
- open_file (from `.symlinks/plugins/open_file/ios`)
- package_info (from `.symlinks/plugins/package_info/ios`)
- path_provider (from `.symlinks/plugins/path_provider/ios`)
- shared_preferences (from `.symlinks/plugins/shared_preferences/ios`)
- uni_links (from `.symlinks/plugins/uni_links/ios`)
- url_launcher (from `.symlinks/plugins/url_launcher/ios`)
SPEC REPOS:
https://github.com/cocoapods/specs.git:
- OneSignal
EXTERNAL SOURCES:
device_info:
:path: ".symlinks/plugins/device_info/ios"
Flutter:
:path: ".symlinks/flutter/ios"
flutter_secure_storage:
:path: ".symlinks/plugins/flutter_secure_storage/ios"
local_auth:
:path: ".symlinks/plugins/local_auth/ios"
location:
:path: ".symlinks/plugins/location/ios"
onesignal:
:path: ".symlinks/plugins/onesignal/ios"
open_file:
:path: ".symlinks/plugins/open_file/ios"
package_info:
:path: ".symlinks/plugins/package_info/ios"
path_provider:
:path: ".symlinks/plugins/path_provider/ios"
shared_preferences:
:path: ".symlinks/plugins/shared_preferences/ios"
uni_links:
:path: ".symlinks/plugins/uni_links/ios"
url_launcher:
:path: ".symlinks/plugins/url_launcher/ios"
SPEC CHECKSUMS:
device_info: 76ce0b32e13034d1883be4a382433648f9dcee63
Flutter: 9d0fac939486c9aba2809b7982dfdbb47a7b0296
flutter_secure_storage: cbb73e37aa0c66689fe63799a9619ac66849b8fa
local_auth: dca7d49d2228a53db258478ee98ee19402ff0c49
location: 26c90953ad5916331d0d1d913898779910416487
OneSignal: a506e3bc61d2030f0757faf9bd783a9b211c6e3c
onesignal: 73d086c833571282264a75e090411d039328a8a2
open_file: 40d524de730775bb4edb021fa137cc1d2fa13f1c
package_info: d7c98b64f60add4c2908b9d94d82a45d3c8827ad
path_provider: 09407919825bfe3c2deae39453b7a5b44f467873
shared_preferences: 5a1d487c427ee18fcd3ea1f2a131569481834b53
uni_links: 5ee5240df5cbffc52d9e7f8017a576b6a6bc5141
url_launcher: 92b89c1029a0373879933c21642958c874539095
PODFILE CHECKSUM: 530d76629cdb9b493aab7ed5604c44e4493a8f12
COCOAPODS: 1.5.3
On Dec 16, 2018, at 1:06 PM, Brad Hesse ***@***.***> wrote:
@sjmcdowall <https://github.com/sjmcdowall> the extension service does not need those other frameworks. The only external lib it needs is OneSignal. It should not even try to link to other Flutter libs.
That is what we will want to be debugging. Are you sure your Podfile is still the one you posted earlier? If so, this is really bizarre, Cocoapods is trying to add the wrong frameworks to the Extension service that your own Podfile says should only link to OneSignal
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8M7VcTTqBhtxB0aMXpLVwYzFG65Lwoks5u5ouggaJpZM4ZUHim>.
|
|
@sjmcdowall I’m not sure why you’d say that - the Extension service is required by iOS if you want to use rich dynamic push notifications, it’s not required by OneSignal. The extension service is only necessary if you want to use badge increment logic (ie. this notification increases the existing badge count by X) or if you want to send rich push notifications with images and so on. You can just remove it entirely if you don’t need those things. In any case, your Podfile looks fine. Cocoapods should not be generating a project that tries to link those libs to the extension service - that’s quite strange. None of our other Flutter users have ever posted about such an issue so I would assume it’s some strange edge case with Cocoapods. What version of Cocoapods are you using? Can you try upgrading to the beta, or downgrading to an older version (ie. 1.3 or 1.1) and see if the same result occurs? |
|
Another useful troubleshooting step would be to create an entirely new Flutter project and see if you can integrate OneSignal using your environment. |
|
In answer to your prior question -- we are on CocoaPods 1.5.3 which is official version Flutter supports (nothing earlier is allowed)
I do plan to try out the new beta CocoaPods .. just to see
As for the below -- yes -- I was actually going to take your example app -- and just add all the other pubspec.yaml dependencies etc. to the same app and
see if we get the same issue ..
but first.. I'll try Beta cocoapods 1.6.X
I'll keep in touch ..
… On Dec 16, 2018, at 11:04 PM, Brad Hesse ***@***.***> wrote:
Another useful troubleshooting step would be to create an entirely new Flutter project and see if you can integrate OneSignal using your environment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8M7VeuPKr06WSvERhKJiMQjMGvDOSnks5u5xflgaJpZM4ZUHim>.
|
|
As a semi follow up -- I am looking more closely at the compile error and it's NOT from the Pod stuff at all .. it's the main Runner project and the Target within that ..
We need to figure out a way to get this Target in runner to be AFTER the Pod's Project
=== BUILD TARGET path_provider OF PROJECT Pods WITH CONFIGURATION Debug ===
…---
=== BUILD TARGET OneSignalNotificationServiceExtension OF PROJECT Runner WITH CONFIGURATION Debug ===
Check dependencies
Write auxiliary files
write-file /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServic
eExtension.build/Script-CC091B9B7253D21F00764737.sh
chmod 0755 /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServiceExtension.build/Script-CC091B9B7253D21F00764737.sh
Create product structure
/bin/mkdir -p /Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/OneSignalNotificationServiceExtension.appex
ProcessInfoPlistFile /Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/OneSignalNotificationServiceExtension.appex/Info.plist OneSignalNotificationServiceExtension/Info.plist
cd /Users/sjm/work/mm/mms4/mobile/ios
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/sjm/Development/flutter/bin:/Users/sjm/.fastlane/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:.:/usr/local/opt/go/libexec/bin"
builtin-infoPlistUtility /Users/sjm/work/mm/mms4/mobile/ios/OneSignalNotificationServiceExtension/Info.plist -expandbuildsettings -format binary -platform iphonesimulator -o /Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/OneSignalNotificationServiceExtension.appex/Info.plist
ProcessProductPackaging "" /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServiceExtension.build/OneSignalNotificationServiceExtension.appex-Simulated.xcent
cd /Users/sjm/work/mm/mms4/mobile/ios
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/sjm/Development/flutter/bin:/Users/sjm/.fastlane/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:.:/usr/local/opt/go/libexec/bin"
Entitlements:
{
"application-identifier" = "LVZ24S452F.com.missionmode.mobile.OneSignalNotificationServiceExtension";
"com.apple.security.application-groups" = (
"group.com.missionmode.mobile.onesignal"
);
}
builtin-productPackagingUtility -entitlements -format xml -o /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServiceExtension.build/OneSignalNotificationServiceExtension.appex-Simulated.xcent
PhaseScriptExecution [CP]\ Check\ Pods\ Manifest.lock /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServiceExtension.build/Script-CC091B9B7253D21F00764737.sh
cd /Users/sjm/work/mm/mms4/mobile/ios
/bin/sh -c /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServiceExtension.build/Script-CC091B9B7253D21F00764737.sh
Ld /Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/OneSignalNotificationServiceExtension.appex/OneSignalNotificationServiceExtension normal x86_64
cd /Users/sjm/work/mm/mms4/mobile/ios
export IPHONEOS_DEPLOYMENT_TARGET=10.0
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/sjm/Development/flutter/bin:/Users/sjm/.fastlane/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:.:/usr/local/opt/go/libexec/bin"
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator12.1.sdk -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/device_info -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/flutter_secure_storage -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/local_auth -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/location -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/onesignal -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/open_file -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/package_info -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/path_provider -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/shared_preferences -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/uni_links -L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/url_launcher -F/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator -F/Users/sjm/work/mm/mms4/mobile/ios/Pods/../.symlinks/flutter/ios -F/Users/sjm/work/mm/mms4/mobile/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework -filelist /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServiceExtension.build/Objects-normal/x86_64/OneSignalNotificationServiceExtension.LinkFileList -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @executable_path/../../Frameworks -mios-simulator-version-min=10.0 -dead_strip -Xlinker -object_path_lto -Xlinker /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServiceExtension.build/Objects-normal/x86_64/OneSignalNotificationServiceExtension_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 -fobjc-arc -fobjc-link-runtime -fapplication-extension -ObjC -ldevice_info -lflutter_secure_storage -llocal_auth -llocation -lonesignal -lopen_file -lpackage_info -lpath_provider -lshared_preferences -luni_links -lurl_launcher -framework Flutter -framework OneSignal -framework SystemConfiguration -framework UIKit -framework UserNotifications -ObjC -framework OneSignal -framework SystemConfiguration -framework UIKit -framework UserNotifications -e _NSExtensionMain -Xlinker -sectcreate -Xlinker __TEXT -Xlinker __entitlements -Xlinker /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServiceExtension.build/OneSignalNotificationServiceExtension.appex-Simulated.xcent -lPods-OneSignalNotificationServiceExtension -Xlinker -dependency_info -Xlinker /Users/sjm/Library/Developer/Xcode/DerivedData/Runner-fmfgxmbciwytkiaoztfoxtepvsaw/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/OneSignalNotificationServiceExtension.build/Objects-normal/x86_64/OneSignalNotificationServiceExtension_dependency_info.dat -o /Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/OneSignalNotificationServiceExtension.appex/OneSignalNotificationServiceExtension
ld: warning: directory not found for option '-L/Users/sjm/work/mm/mms4/mobile/build/ios/Debug-iphonesimulator/location'
ld: library not found for -llocation
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Steven McDowall - VP Engineering
MissionMode
20 West Kinzie Street, Suite 1420
Chicago, IL 60654
tel +1.336.608.2001
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain sensitive and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
On Dec 17, 2018, at 8:44 AM, Steven McDowall ***@***.***> wrote:
In answer to your prior question -- we are on CocoaPods 1.5.3 which is official version Flutter supports (nothing earlier is allowed)
I do plan to try out the new beta CocoaPods .. just to see
As for the below -- yes -- I was actually going to take your example app -- and just add all the other pubspec.yaml dependencies etc. to the same app and
see if we get the same issue ..
but first.. I'll try Beta cocoapods 1.6.X
I'll keep in touch ..
> On Dec 16, 2018, at 11:04 PM, Brad Hesse ***@***.*** ***@***.***>> wrote:
>
> Another useful troubleshooting step would be to create an entirely new Flutter project and see if you can integrate OneSignal using your environment.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8M7VeuPKr06WSvERhKJiMQjMGvDOSnks5u5xflgaJpZM4ZUHim>.
>
|
|
@sjmcdowall The build order should not matter. Can you open your project in Xcode, navigate to your Project Settings, select the OneSignal Notification Service Extension target, and select the General tab, and send me a screenshot of the whole page? Especially everything you see in Linked Frameworks section. |
|
OK -- was just about to write you !
Here is the screenshot of the vanilla thing you wanted (see below)
However, I was hacking around -- and for fun I added ALL the damn libraries in the Pod project to the dependency of the OneSignal target ... (which I removed for the screen shot)
However -- damn it -- now that I've done all this -- I can't reproduce the issue -- which I guess is good gnus?
Sigh
/Steve
… On Dec 17, 2018, at 1:47 PM, Brad Hesse ***@***.***> wrote:
@sjmcdowall <https://github.com/sjmcdowall> The build order should not matter. Can you open your project in Xcode, navigate to your Project Settings, select the OneSignal Notification Service Extension target, and select the General tab, and send me a screenshot of the whole page? Especially everything you see in Linked Frameworks section.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8M7UBAE9pPE7HQX_foI9Rz8JbVsKJbks5u5-bCgaJpZM4ZUHim>.
|
|
Hi @sjmcdowall, sorry for the slowdown during the holidays. What's the status of this issue currently? |
|
As long as I put some of the Pod dependencies in the target for OneSignal it compiles fine .. just keeping with that for now |
|
Closing this issue since I've never heard of any other user experiencing this issue - I would assume there's some configuration with your project that most developers/companies don't have that causes this issue. |
|
Hi @sjmcdowall , could you please elaborate on your work-around? Breaking my head for an entire day so far and just can't get the iOS build to work.. Cheers! |
|
@lifenautjoe -- sure -- but let's make sure we have the same issue -- can you post your error -- and build with a -v and post the "important" parts of that output the shows the error? Or is it exactly the same as error above with the ld link failure thing? Oh and you might as well show me your Podfile too .. |
|
Awesome that you're willing to help @sjmcdowall ! Running Running it with the And finally, my podfile contains: Thank you for having a look! |
|
No worries -- and yeah -- same style error. So no SWIFT plugins yet in your project,eh? Lucky you. :) If you are using the latest OneSignal .. make sure your minimum in your Podfile is 2.9.5 not 2.9.3 .. something deprecated a bit ago and now you need 2.9.5. minumum.. that's not YOUR issue yet but it could be. :) Here is my Podfile -- I think it's pretty close: |
|
OK -- now here is the real hack :) Basically you need to add a bunch (all?) your OTHER pod libs in your project to the dependency area of the OneSignal within your Runner project within Xcode. So you need to open in Xcode your Runner.xcworkspace .. then make it sort of look like the attached screenshot.. obviously the libraries will depend on what you have imported in pubspec.yaml .. but certainly make sure to include any specific ones the "LD" is complaining about and see how that goes...
|
|
Omw home now but will give it a go as soon as I arrive !
Will let you know ASAP!
Thanks ! 🙏
…On Thu, 31 Jan 2019 at 20:34, S McDowall ***@***.***> wrote:
OK -- now here is the real hack :) Basically you need to add a bunch
(all?) your OTHER pod libs in your project to the dependency area of the
OneSignal within your Runner project within Xcode. So you need to open in
Xcode your Runner.xcworkspace .. then make it sort of look like the
attached screenshot.. obviously the libraries will depend on what you have
imported in pubspec.yaml .. but certainly make sure to include any specific
ones the "LD" is complaining about and see how that goes...
[image: screen shot 2019-01-31 at 2 29 10 pm]
<https://user-images.githubusercontent.com/2034925/52080238-49b47a80-2565-11e9-8540-33da757d071c.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMJb5aMAAngxYdND8hsUU7E-NSra1gSqks5vI0VPgaJpZM4ZUHim>
.
|
|
Hi @sjmcdowall, Sorry for the delay. Something else came up.. Regarding the work-around... Where do I find the .a files? I can just see the .h files of the libraries.. Sorry for the newbie question, not really an iOS developer 😅. Thanks! |
|
So... that fixed those errors but started getting an error that an image cropping library I was using did not contain bitcode and had to rebuild I just added Enable Bitcode No to the OneSignalNotificationService extension and it worked like a charm.
As a final question.. Is there any unintended consequences this might have? And once again, thanks for the help @sjmcdowall & @Nightsd01 . You guys are the MVPs ! 🙏 |
lifenautjoe
added a commit
to OkunaOrg/okuna-app
that referenced
this issue
Feb 1, 2019
|
Actually BITCODE enabled is actually (likely) preferred. I had to turn it off because a library I was using didn't have it and was complaining because I did not turn it off! I think it was a SWIFT plugin. Rule of thumb -- avoid SWIFT plugins I think unless absolutely needed :) So the only downside MAYBE you wind up in a catch-22 problem somewhere down the line where one library must have BITCODE off and one must have BITCODE on .. but until then, go forward!! Onwards and upwards! |
|
Oh and @Nightsd01 -- see, ANOTHER person with the same issue. It's just a matter of time before more. :) Although I don't think in reality the issue is anything in OneSignal but in flutter build arch.. |
|
Hello, This is my podfile
And this is the error I got
|
|
Not sure this will help but ..
1 -- if you haven't make sure to do a flutter upgrade ..
2 -- what flutter channel are you on? We are on "beta"
3 -- we are using cocoapods 1.6.0
4 -- we had to set our SWIFT to 4.0 not 4.2 -- but some had to do 4.2 so YMMV
That error log doesn't appear to have any errors only wanrings?
maybe do a "flutter run -v" to get more verbose errors -- especially at the bottom?
What's your project (in the Xcode files) version # set to? Some of thos warnings appear .. odd.. if you are targeting 10.2 or whatever..
… On Feb 12, 2019, at 3:23 PM, Nívea Melo ***@***.***> wrote:
Hello,
I ended up with the same problem of you guys @lifenautjoe <https://github.com/lifenautjoe> and @sjmcdowall <https://github.com/sjmcdowall> and tried the work-around mentioned in this comment <#42 (comment)>. Initially the error was pointing only the permission handler package, but after following sjmcdowall's steps, I got some new errors related to swift libraries. I was wondering if you guys could help me with this... I am new to Xcode and ios development, so sorry if I wasn't clear about some terms...
This is my podfile
And this is the error I got
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8M7VF8Q0PMwXh72bE4yhI9x0qHW2LMks5vMyKwgaJpZM4ZUHim>.
|
|
Flutter is up-to-date, but I am on "stable" channel. I'm using cocoapods 1.5.3. I'm unable to update it to 1.6.0 right now because I'm using one of the MacinCloud servers and I have no sudo access on it. I was forced to use version 4.2 of swift because I was dealing with some other errors with messages like After doing Log messageI'm also attaching two images showing both the error and the linked frameworks in xcode - in case that helps on something.
|
|
Honestly -- I think this is beyond anything to do with OneSignal .. And nothing similar with what we others have run into ..
1 -- Does this run/work on Android ? I.e. target an Android simulator with your "flutter run"
2 -- Does this work WITHOUT OneSignal at all?
3 -- Does this work WITH OneSignal but without the Swift Plugin(s) you have?
My gut is telling me something is odd about one or more of your OTHER plugins ...
… On Feb 12, 2019, at 6:07 PM, Nívea Melo ***@***.***> wrote:
Flutter is up-to-date, but I am on "stable" channel.
Flutter 1.0.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 5391447fae (3 months ago) • 2018-11-29 19:41:26 -0800
Engine • revision 7375a0f414
Tools • Dart 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)
I'm using cocoapods 1.5.3. I'm unable to update it to 1.6.0 right now because I'm using one of the MacinCloud servers and I have no sudo access on it. I was forced to use version 4.2 of swift because I was dealing with some other errors with messages like'openSettingsURLString' was introduced in Swift 4.2.
After doing flutter run -v I get this piece of text in red:
Log message
I'm also attaching two images showing both the error and the linked frameworks in xcode - in case that helps on something.
<https://user-images.githubusercontent.com/24644618/52674003-4e2b4c80-2ef0-11e9-8e28-da62d65d6f3d.png>
<https://user-images.githubusercontent.com/24644618/52674023-584d4b00-2ef0-11e9-9a5e-0391a65b931e.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8M7Xf1N_02PFIOAW-j8KRG5jTIjkjwks5vM0kWgaJpZM4ZUHim>.
|
|
I got this error: |
|
Gracias @rgomezp esa fue la la solución 😁 |
|
TRANSLATION OF ABOVE: |
|
Can we use onesignal sdk without extension for time being? |
|
@rgomezp Using above mentioned OneSignal git package does not solve the issue. |
|
@rajeevjaiswal , |
This was referenced May 30, 2019
ghost
mentioned this issue
|
We just released onesignal_flutter 2.0.0 which should fix the header issue when you have |
Closed
|
@sjmcdowall |
|
@Goolpe -- Alas I haven't used this library in 10 months .. or Flutter since moving to a new job. Sorry |
It does not fix the issue. |
|
Battling myself to death to get it approved in xCode |
|
Issue still exists... |
|
Updated cocoapods with Then, changed in pods file: Change Then Done 👏 |
|
IOS version in build phases of pod(in xcode) and ios version in pod file should be same (Try with 9.0) |
|
After upgrading to macOS Catalina I am still facing this issue Cause when I run this from Xcode this works fine but when I run it from terminal it fails . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Every once in a while -- after adding a new package (sometimes) or clearing some cache, our application refuses to build on iOS simulators/debug .. and sometimes takes a few tries on production release builds .. with a build error about nothing finding trying to link
OneSignalNotificationServiceExtension
What appears to be happening is that this Ld is premature and all the other Pods needed and listed haven't been compiled yet .. so the ld fails because Flutter puts them all together.. here is the snippest from the fails:
I can include the total flutter run -v output somewhere (it's lengthy) if you tell me where..
I am not sure why it's do an clang thing THEN in the middle of the project builds?? I think that's the culprit ..
Environment
Steps to Reproduce Issue:
The odd thing is that the first time we run we may get 5/6 "ld" errors.. but each run after reduces that. Sometimes we get 0 and once it's zero we're good again until the next "flutter upgrade" or something that adds a pod .. then all hell breaks loose again . :(
I have this reproducible right now -- can't fix actually ..
Here is our pubspec.yaml file:
Here is the Podfile from /ios
This is rather a show stopper for us right now as we're stuck ..
Cheers!
The text was updated successfully, but these errors were encountered: