After upgrading to Flutter 2.8.0, I can't run my app on MacOS, receiving this error :
/Users/cac/Programming/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_crashlytics-2.4.3/macos/Classes/FLTFirebaseCrashlyticsPlugin.m:6:9: fatal error: 'Crashlytics_Platform.h' file not found
#import "Crashlytics_Platform.h"
^~~~~~~~~~~~~~~~~~~~~~~~
Maybe it's an issue, but I need a turn around for now:
https://github.com/FirebaseExtended/flutterfire/discussions/7484
I just install Xcode 9 iOS 11 and build my iOS project. I am getting below error on Realm below error.
pod 'Realm', '~> 1.0.0'
Error:
/Pods/Realm/Realm/ObjectStore/results.cpp:489:20: error: no viable overloaded '='
m_notifier = std::make_shared<_impl::ResultsNotifier>(*this);
My project working fine on Xcode 8.3 iOS 10. Issue is facing only Xcode 9 iOS 11.
How can I fix this?
Try to change your podfile to the latest version of Realm:
pod 'Realm'
This fix is up to version 2.8.1, so you can type a min version:
pod 'Realm', '~> 2.8.1'
A little warning: If you are using a pod project and it internally uses Realm, do not forget to update your .podspec file, otherwise your final project will not update and you will continue to get the same error.
I m having 2 version of VS2017 and a mac with latest macOS.
I transfer my Xamarin forms App file from VS2017 enterprise to a machine(more than 3 years old but running win10 pro) with VS2017 Community version. When I debug ( with selecting Android project and VS-android-23 X86 tablet as emulator ) this App in VS2017 Community version , I have no compilation error but have these message:
Found conflicts between different versions of the same dependent assembly
that could not be resolved.
These reference conflicts are listed in the build log when log verbosity is set to detailed.
I could not understand this message. I have no problem running the same app in VS2017 Enterprize ver but I have this error message in VS2017 Community ver.
Update
Click View > Output --> this will show the error
1>Starting deploy VisualStudio_android-23_x86_tablet ...
1>Starting emulator VisualStudio_android-23_x86_tablet ...
1>C:\Users\xxxxx\AppData\Local\Android\ANDROI~1\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd VisualStudio_android-23_x86_tablet -prop monodroid.avdname=VisualStudio_android-23_x86_tablet
1>emulator: ERROR: x86 emulation currently requires hardware acceleration!
1>Please ensure Intel HAXM is properly installed and usable.
1>CPU acceleration status: Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.
1>Emulator VisualStudio_android-23_x86_tablet cannot be started.
Please help.
The Adobe doc Developing AIR applications for mobile devices lists quite a few icons to be declared in an application descriptor file.
But when I try Export Release Build with the following myApp-app.xml:
<icon>
<image16x16>assets/icons/16x16.png</image16x16>
<image29x29>assets/icons/29x29.png</image29x29>
<image32x32>assets/icons/32x32.png</image32x32>
<image36x36>assets/icons/36x36.png</image36x36>
<image48x48>assets/icons/48x48.png</image48x48>
<image57x57>assets/icons/57x57.png</image57x57>
<image72x72>assets/icons/72x72.png</image72x72>
<image114x114>assets/icons/114x114.png</image114x114>
<image128x128>assets/icons/128x128.png</image128x128>
<image512x512>assets/icons/512x512.png</image512x512>
<!--
<image50x50>assets/icons/50x50.png</image50x50>
<image58x58>assets/icons/58x58.png</image58x58>
<image100x100>assets/icons/100x100.png</image100x100>
<image144x144>assets/icons/144x144.png</image144x144>
<image1024x1024>assets/icons/1024x1024.png</image1024x1024>
-->
</icon>
I get the error message (regardless if deploying for Android or iOS) unless I comment the 5 lines as above:
error 103: application.icon.image50x50 is an unexpected element/attribute
error 103: application.icon.image58x58 is an unexpected element/attribute
error 103: application.icon.image100x100 is an unexpected element/attribute
error 103: application.icon.image1024x1024 is an unexpected element/attribute
error 103: application.icon.image144x144 is an unexpected element/attribute
My question is what to do here? Moving those 5 icons underneath <android>....</android> or <iphone>....</iphone> doesn't help either.
Using Flash Builder 4.7 beta under Windows 7 / 64 bit.
The solution is to update the version of AIR used within your SDK. Those new icon sizes are not supported in the version of AIR included in Adobe Flex 4.6 [or Apache Flex 4.8].
Instructions for updating the AIR SDK within Flex can be found here. Generically do this:
Download current SDK and unzip it
Copy and files and folders from your unzipped directory to the root of your Flex directory
Update the name of the Flex SDK in the “flex-sdk-description.xml” file.
After upgrade XCode from 4.2 to 4.3 I've got below problem. I can't build it.
Do you guys have idea how can I resolve this problem? even some clue would be helpful to me.
ld: warning: ignoring file /Applications/Xcode.app/Contents/Developer/Library/Frameworks/SenTestingKit.framework/SenTestingKit, missing required architecture armv7 in file
Undefined symbols for architecture armv7:
"_STComposeString", referenced from:
-[NSMutableURLRequest_ParametersTest verifyDefaultParametersForRequest:] in NSMutableURLRequest+ParametersTest.o
-[NSMutableURLRequest_ParametersTest verifyModifiedParametersForRequest:] in NSMutableURLRequest+ParametersTest.o
-[NSMutableURLRequest_ParametersTest verifyEmptyParametersForRequest:] in NSMutableURLRequest+ParametersTest.o
-[NSString_URLEncodingTest testURLEncodedString] in NSString+URLEncodingTest.o
-[NSURL_BaseTest testURLStringWithoutQuery] in NSURL+BaseTest.o
-[OAHMAC_SHA1SignatureProviderTest testSignClearText] in OAHMAC_SHA1SignatureProviderTest.o
-[OAMutableURLRequestTest testGenerateNonce] in OAMutableURLRequestTest.o
...
"_OBJC_CLASS_$_SenTestCase", referenced from:
_OBJC_CLASS_$_NSMutableURLRequest_ParametersTest in NSMutableURLRequest+ParametersTest.o
_OBJC_CLASS_$_NSString_URLEncodingTest in NSString+URLEncodingTest.o
_OBJC_CLASS_$_NSURL_BaseTest in NSURL+BaseTest.o
_OBJC_CLASS_$_OAHMAC_SHA1SignatureProviderTest in OAHMAC_SHA1SignatureProviderTest.o
_OBJC_CLASS_$_OAMutableURLRequestTest in OAMutableURLRequestTest.o
_OBJC_CLASS_$_OAPlaintextSignatureProviderTest in OAPlaintextSignatureProviderTest.o
_OBJC_CLASS_$_OARequestParameterTest in OARequestParameterTest.o
...
"_OBJC_METACLASS_$_SenTestCase", referenced from:
_OBJC_METACLASS_$_NSMutableURLRequest_ParametersTest in NSMutableURLRequest+ParametersTest.o
_OBJC_METACLASS_$_NSString_URLEncodingTest in NSString+URLEncodingTest.o
_OBJC_METACLASS_$_NSURL_BaseTest in NSURL+BaseTest.o
_OBJC_METACLASS_$_OAHMAC_SHA1SignatureProviderTest in OAHMAC_SHA1SignatureProviderTest.o
_OBJC_METACLASS_$_OAMutableURLRequestTest in OAMutableURLRequestTest.o
_OBJC_METACLASS_$_OAPlaintextSignatureProviderTest in OAPlaintextSignatureProviderTest.o
_OBJC_METACLASS_$_OARequestParameterTest in OARequestParameterTest.o
...
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
I was getting the same linking error for the Simulator after upgrading from Xcode 4.2 -> 4.3.1. I noticed that new projects in 4.3.1 do work with Unit Tests, so just compared the project differences.
What fixed it for me was:-
Select Project in project navigator
Select Test Target
Select Build Settings
Go down to Framework Search Paths and single-click it
Delete whatever is there
Enter $(SDKROOT)/Developer/Library/Frameworks $(DEVELOPER_LIBRARY_DIR)/Frameworks
If you had any custom frameworks, add those back
Actually, Unit Tests run fine on the Device, too.
Looks like this was either an accidental (or on purpose) omission on Apple's part.
If (and only if) you are a registered Apple Developer, you can log into the Apple Developer Forums and if you copy this linked search query into your browser address bar, you will see other people have had the same problem.
For now, it looks like you can only use SenTestingKit on the simulator.
I had a similar issue with Xcode 4.4.
My solution path:
Removed SetTestingKit.framework from the main target's (the system under test) "link binary with libraries", leaving it in the test target as is. Not sure why it ended up there in the first place.
I believe this bug is now fixed in Xcode 4.4.1
Using xcode 4.6 and trying to add facebook SDK 3.1 I had this problem because I didn't select to add the files to my test target.
You should check both targets when you copy the framework.
I just upgraded to 4.3.1 There is a problem with SenTestingKit framework. I removed the test source code from the project, it builds ok. And it can run on 5.1 device. But I got _dyld_dyld_start error when I ran it on simulator. I had to remove SenTestingKit from the project to make it work on simulator.