Alamofire.framework” specifies a simulator platform for the CFBundleSupportedPlatforms key
Related
/native/Frameworks/IBMMobileFirstPlatformFoundationHybrid.framework/IBMMobileFirstPlatformFoundationHybrid(WLAFURLRequestSerialization.o)' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. for architecture armv7
https://developer.ibm.com/mobilefirstplatform/2015/09/09/mobilefirst-platform-support-for-ios-9/
Updating existing apps or submitting new apps on the App Store (with Xcode7 and iOS 9 features)
Review the following sections to learn what actions you need to take so that your app can support iOS 9.
Bitcode
iOS9 introduces a new feature called bitcode, an intermediate code uploaded to the Apple App Store. Apple compiles the bitcode of the application to optimize it for each type of devices. To learn more about bitcode, see the Apple documentation.
At this time, the IBM MobileFirst Platform SDK does not support bitcode. Your application will fail to build with Xcode 7 unless you disable bitcode. If bitcode is enabled, you will see an error message.
Action required
Disable bitcode for your project: In Xcode, select Build Settings > Build Options and set Enable Bitcode to No.
I am working on iphone app with deployment target 5.1.1 and now i am adding google ios sdk in my project. I am not giving this functionality to user who has iOS 5.1.1 in device.
But google iOS Sdk needs to set Other Linker flag (-ObjC) in build setting and it creates problem in iOS 5.1.1.
is there any way to set Other Linker flag conditionally? i need to give support for iOS 5.1.1.
I tried below steps but not able to run app in iOS 5.1.1.
At the end compiler will generate single binary. Whether you provide certain feature in iOS 5.1.1 or not does not matter to compiler. So if you need to set deployment target to iOS 5.1.1 then all the static libraries you link must also support that particular deployment target.
More details on ObjC flag
Few days back I had everything working with a provisioning profile for Distribution( App Store).And after upgrading iphone to IOS7 the ipa not installing in any of ios7 but is working fine with ios6.
While using iTunes it says waiting... or installing... for long but when used iphone configuration Uitility it says invalid profile(Doubt is how is it working on IOS6)????
It is also working with Distribution Certificate of type ADHOC where i added the device udid in the device List.So Architecture is definitely not the problem
Have you updated architectures for new device in your build setting.
it happens because of architecture,ipa will install on those devices which supports the cpu architecture mention in your build setting,but not on those devices who's architecture is not mentioned.
I am new to iPhone development, I am using xCode 4.4.1
I have setup a Provisioning profile and was able to debug on my iPhone device before
I have disconnected my device from the machine and restarted it
Once reconnected my device doesn't appear on the available Scheme Destinations
Having that said:
I have verified that the provisioning profile is properly set on my
device # Settings->General->Profile
Using xCode->Organizer->Devices, I have verified that the Provisioning profile is properly set on the
dev machine.
Since restarting my physical iPhone device I can't use it for debugging, why ?
Any help will be appreciated.
~Nadav
The problem was that while I was trying to generate armv6 code I was experimenting with xcode v4.4.1, this xcode version doesn't support iOS 6, and thus, it didn't recognize my device.
Are there any simulators that run symbian applications?
Since its introduction, Symbian has provided an emulator to allow development of Symbian on a PC.
Currently, the Symbian Foundation is developing a simulator which will eventually replace the emulator. At present, however, this is a work in progress and is not really suitable for general purpose Symbian development.
What is the difference between the two? The links above will provide the full story, but the key difference is as follows:
The emulator is effectively a port of Symbian OS to a new architecture: whereas all Symbian devices in the market today are based on ARM architecture, the emulator is a port to x86. This port is not a particularly faithful representation of a real device however - for example, while Symbian OS on the device provides memory protection between user-side processes, the emulator runs as a single Windows process, with each Symbian process running as a separate emulated thread. This and other aspects of the emulator mean that your app may behave differently when moved from the emulator onto the device.
The simulator is based on QEMU, which provides instruction-level simulation of the ARM architecture. This means that the same binaries can be run on the simulator and on the device (at least in most cases - each device, including the simulator, still has its own adaptation layer which is not portable in this way). The simulator also more closely models a real device - providing, for example, the same level of memory protection.
The emulator is included in the Symbian SDK.
Assuming that you installed the SDK in the default location, to run the emulator just launch
C:\S60\devices\S60_5th_Edition_SDK_v1.0\epoc32\release\winscw\udeb\epoc.exe
You can find here more detailed informations.