Crash here SDK Navigate - Google Analytics - here-api

I see a log of this crash and I have no idea how to trouble shoot it. Any guidance ?
I use the flutter navigate SDK 4.12.11.0361
Crash : OLPSDKPOOL_6
SIGABRT ABORT 0x00000001cbe9c200
keyboard_arrow_up
0
libsystem_kernel.dylib
__pthread_kill + 8
5arrow_drop_down
libsystem_malloc.dylib
find_zone_and_free + 308
arrow_right 6
heresdk
here_sdk_sdk_venue_threading_VenueThreads_get_type_id + 19512588
7
heresdk
here_sdk_sdk_venue_threading_VenueThreads_get_type_id + 24067388
I am not clear on how to trouble shoot this.

Related

remark: Incremental compilation has been disabled: it is not compatible with whole module optimization

Updated to the Xcode 13 beta, now I can't build the project due to an error in several pods
Older Xcode launches an app on iOS 15 too long
I use M1, maybe this is due to architecture
I faced with issue after updating Xcode to version 13. As the compiler complains about whole module compilation, we need to use the incremental mode.
To do this:
Select your target and go to Build Settings -> Compilation Mode -> Switch to "Incremental"
That remark isn't an actual error, just a warning. The real error can be found in the nested Compile Swift source files under the top level section with the same name. Expand the logs for this command and you should see the actual error.
I ran pod update and it fixed the issue for me
In my project, pods deployment target was still iOS 8.0. I have added following to my Podfile to upgrade them iOS 13. Then I clean project and removed derived data. After adding following script you need to call pod install.
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET'
end
end
end
I downgraded Xcode to 13.2.1 and that solved my problem. Seems 13.3 have this compat issue with some of 3rd party libraries.
This issue is due to an upgrade to a new Xcode version.
Go to ->About this Mac -> Storage -> Manage
1 - Delete the files in the developer Xcode Project Indexes files
2 - Give it a try again
My Xcode 13.3 can't build for device. But it builds for simulators.
So I downgraded Xcode to 13.2.1. Problem solved.
I think the problem is cause by pod. when you upgrade to 13.3, some pod target's option "ENABLE_BITCODE" have been set "YES", so you just need add code to your Podfile, just like this:
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['ENABLE_BITCODE'] = 'NO'
end
end
end
and clean project and delete cache, archive will be success.
I also have a similar issue, tried multiple ways but no help.
Finally worked for me:
pod deintegrate
Clean up
pod install
This helped me. Answers from developer.apple.com
Add this in Podfile
$iOSVersion = '11.0'
post_install do |installer|
# add these lines:
installer.pods_project.build_configurations.each do |config|
config.build_settings["EXCLUDED_ARCHS[sdk=*]"] = "armv7"
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = $iOSVersion
end
installer.pods_project.targets.each do |target|
# add these lines:
target.build_configurations.each do |config|
if Gem::Version.new($iOSVersion) > Gem::Version.new(config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'])
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = $iOSVersion
end
end
end
end
I have that problem on Xcode 13.3, but after downgraded to 13.1, I can archive successful
pod update
Updating SwiftMessages pod version from 8.0.2 to 9.0.4 (which didn't not work with Swift 5.5) helped me
What worked for me initially was cleaning Xcode project build files.
"About This Mac" -> Storage -> Manage -> Developer
Xcode project build files
This is also a neat way to clear up some space when you are running out.
Then it started happening again. I then tried selecting "Whole Module" for "Compilation Mode" in "Build Settings". Build didn't fail so far.
I've experienced the same problem due to one of my swift packages lacked 'platforms' specifications in manifest, while at the same time utilising some platform specific framework (SwiftUI in my case)..
Package implementation specified the availability of the api as follows:
#available(iOS 14.0, tvOS 14.0, watchOS 7.0, macOS 11, *)
public extension Font {
//
}
Once I've added the corresponding platform specification in package manifest the problem went away:
let package = Package(
name: "package-name",
platforms: [
.iOS(.v14),
.watchOS(.v7),
.tvOS(.v14),
.macCatalyst(.v14)
],
//
//
)
That remark isn't an actual error, just a warning. The real error can be found in the nested Compile Swift source files under the top level section with the same name. Expand the logs for this command and you should see the actual error.
Inspired by ryanavocado.
For me, it was caused by SKPhotoBrowser in my Podfile. After removing it, the error goes away.
LLVM ERROR: out of memory
Allocation failed
Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the project and the crash backtrace.
Stack dump:
0. Program arguments: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -c -primary-file /Users/***/Library/Developer/Xcode/DerivedData/***/Build/Intermediates.noindex/ArchiveIntermediates/***/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/SKPhotoBrowser.build/Objects-normal/arm64/SKPhotoBrowser.bc -embed-bitcode -target arm64-apple-ios13.0 -Xllvm -aarch64-use-tbi -O -disable-llvm-optzns -module-name SKPhotoBrowser -o /Users/***/Library/Developer/Xcode/DerivedData/***/Build/Intermediates.noindex/ArchiveIntermediates/***/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/SKPhotoBrowser.build/Objects-normal/arm64/SKPhotoBrowser.o
1. Apple Swift version 5.6 (swiftlang-5.6.0.323.62 clang-1316.0.20.8)
2. Compiling with the current language version
3. Running pass 'Function Pass Manager' on module '/Users/***/Library/Developer/Xcode/DerivedData/***-hhhfwlkzxdivscfrppsfvbhllnzc/Build/Intermediates.noindex/ArchiveIntermediates/***/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/SKPhotoBrowser.build/Objects-normal/arm64/SKPhotoBrowser.bc'.
4. Running pass 'ObjC ARC contraction' on function '#UI_USER_INTERFACE_IDIOM'
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0 swift-frontend 0x00000001077f8de7 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 39
1 swift-frontend 0x00000001077f7e38 llvm::sys::RunSignalHandlers() + 248
2 swift-frontend 0x00000001077f9440 SignalHandler(int) + 288
3 libsystem_platform.dylib 0x00007ff810cf2dfd _sigtramp + 29
4 libsystem_platform.dylib 0x000000031069bae0 _sigtramp + 18446603383459187968
5 libsystem_c.dylib 0x00007ff810c28d24 abort + 123
6 swift-frontend 0x0000000107745cda llvm::report_bad_alloc_error(char const*, bool) + 106
7 swift-frontend 0x0000000107745cf2 out_of_memory_new_handler() + 18
8 libc++abi.dylib 0x00007ff810c9a96b operator new(unsigned long) + 43
9 swift-frontend 0x0000000107506efd llvm::Function::BuildLazyArguments() const + 77
10 swift-frontend 0x00000001052efe87 llvm::objcarc::BundledRetainClaimRVs::insertRVCallWithColors(llvm::Instruction*, llvm::CallBase*, llvm::DenseMap<llvm::BasicBlock*, llvm::TinyPtrVector<llvm::BasicBlock*>, llvm::DenseMapInfo<llvm::BasicBlock*>, llvm::detail::DenseMapPair<llvm::BasicBlock*, llvm::TinyPtrVector<llvm::BasicBlock*> > > const&) + 151
11 swift-frontend 0x0000000105302f88 (anonymous namespace)::ObjCARCContract::run(llvm::Function&, llvm::AAResults*, llvm::DominatorTree*) + 1384
12 swift-frontend 0x000000010753e380 llvm::FPPassManager::runOnFunction(llvm::Function&) + 1488
13 swift-frontend 0x0000000107545073 llvm::FPPassManager::runOnModule(llvm::Module&) + 67
14 swift-frontend 0x000000010753eb39 llvm::legacy::PassManagerImpl::run(llvm::Module&) + 1161
15 swift-frontend 0x0000000102a5c6df swift::performLLVMOptimizations(swift::IRGenOptions const&, llvm::Module*, llvm::TargetMachine*) + 3791
16 swift-frontend 0x0000000102a5d8cc swift::performLLVM(swift::IRGenOptions const&, swift::DiagnosticEngine&, llvm::sys::SmartMutex<false>*, llvm::GlobalVariable*, llvm::Module*, llvm::TargetMachine*, llvm::StringRef, swift::UnifiedStatsReporter*) + 2812
17 swift-frontend 0x0000000102a66aa5 swift::performLLVM(swift::IRGenOptions const&, swift::ASTContext&, llvm::Module*, llvm::StringRef) + 213
18 swift-frontend 0x0000000102521795 swift::performFrontend(llvm::ArrayRef<char const*>, char const*, void*, swift::FrontendObserver*) + 16565
19 swift-frontend 0x00000001024e05d4 swift::mainEntry(int, char const**) + 1108
20 dyld 0x000000020a16151e start + 462
21 dyld 0x000000020a15c000 start + 18446744073709530288
error: Abort trap: 6 (in target 'SKPhotoBrowser' from project 'Pods')
I had same remark for multiple libraries (ObjectMapper, Alamofire) but that wasn't the actual error (as ryanavocado suggested). In my case I also had segmentation fault error in SKPhotoBrowser so I tried updating the SKPhotoBrowser pod and that didn't work. Luckily this worked:
pod 'SKPhotoBrowser', :git => 'https://github.com/suzuki-0000/SKPhotoBrowser.git', :branch => 'master'
As suggested here.
So in conclusion the problem is not that actual remark but some other error.
I faced similar issue before I got it fixed. None of the solutions mentioned worked in isolation.
After two days of research and google searches, here is the combination that worked :
1. On the main project (Runner) I updated the compilation mode to incremental by clicking on Build Setting and searching for compilation.
I cleaned the build folder and tried archiving again and got the same error, then I proceeded to the second step.
2. I changed the Apple clang code generation optimisation level to None
I cleaned the build folder and tried archiving again and got the same error. Then I checked that the error message referenced some plugins in the pod
e.g error: Segmentation fault: 11 (in target 'twilio_voice' from project 'Pods')
So, I proceeded to repeating the steps 1 and two above for each pod plugin that had the error.
3. Repeat steps 1 and two above for each pod plugin that had the error. By clicking on the pod and selecting the plugin in context.
I then cleaned the build folder and tried archiving again and still got the same error, then finally after several researches and google searches I executed the following step
4.
A. I Added
config.build_settings['ENABLE_BITCODE'] = 'NO'
config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET'
to the pod file post install script .
The complete script looks like this :
post_install do |installer|
installer.pods_project.targets.each do |target|
flutter_additional_ios_build_settings(target)
target.build_configurations.each do |config|
config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= [
'$(inherited)',
'PERMISSION_CAMERA=1',
'PERMISSION_MICROPHONE=1',
# Add other permissions required by your app
]
config.build_settings['ENABLE_BITCODE'] = 'NO'
config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET'
end
end
end
B. Foreach Pod plugin that had the error, I then changed Enable Bitcode to No, like this :
I then cleaned the build folder and tried archiving again and boom, it worked .
I should also mention that I changed target IOS version to 11, not sure if it had any effect.
Good luck.
Make sure your pods are the same swift version as your project.
I found that it was due to a mismatch between a framework and project optimisation build settings.
To fix it the target of the project should be optimised e.g. -Os in BuildSettings -> Apple Clang Code Generation -> Optimisation Level on your project target
It seems swift expects optimisations if compilation mode is set to whole module. Eray's answer works, but might not create optimal assembly/bitcode for a release build of the framework.
Project level compilation mode also needs to be Whole module.
Also noticed this can occur if the dependancy order is incorrect. During a parallel build if a required dependancy of a dependancy has not yet been built, this error can exhibit. Fixed by explicitly adding to the the 1st level dependants Build Phases->Link with Libraries list.
I did Product -> Clean, then Xcode -> Preferences -> Locations -> Derived Data, go to directory and delete everything. Then close Xcode and reopened and did my build (Archive). All better.
I went with Podfile update as suggested by atalaysa.
Then Preferences > Derived Data > Force Quit Xcode > Deleted Derived Data > Pod Install > Opened the Xcode project > Let the project run through indexing > Archived successfully.
Delete iOS Podfile.lock and pubspec.lock and pod deintegrate and pod install. Set in iOS/Flutter folder ApplicationFramework.plist file iOS minimum target to 9.0 and below code in Podfile post install script
post_install do |installer|
installer.pods_project.targets.each do |target|
flutter_additional_ios_build_settings(target)
target.build_configurations.each do |config|
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '9.0'
end
end
end
you can check once by setting bitcode enbaled false, if u are using framework.
I have a solution!!!
You need to upgrade the iOS version for problem pods to 11 or higher. I hope this helps you because it helped me, but none of the solutions worked before.photo where change

Infrastructure error launching Blueprint template on fiware cloud lab

for testing purposes I'm trying to launch a blueprint instance with the following specs:
Tier1: base_centos_7 + tomcat6 minimum of instance of 0 and a maximum of 1 (init value: 0)
Tier2: base_debian_7 + mysql1.2.4
minimum of instance: 1 and maximum: 2 (init value: 1)
Launching this blueprint template I receive the following error:
Error: Infrastructure error No entity NetworkInstance found with the following criteria: [name = mynetname]
But if I go in the Networks tab, I'm able to find mynetname in the list and it is with:
Shared: Yes
Status: ACTIVE
Admin State: UP
Any idea why I receive that error?
Thanks a lot in advance.
I recommend you to contact the specific FIWARE Lab region administrators. They could check if there is any issue with the selected network.

Xcode 7.3 and iCloud Drive

I just update Xcode 7.2 to 7.3. My app fetch and store files on icloud drive. If I run app on real device it works fine, if I run in the simulator (logged with my icloud account) the metadataQueryResults returns always 0 files.
Also the system app "iCloud Drive" cannot fetch or save icloud folders and files.
I tried Debug-->Trigger iCloud sync with no luck.
With xcode 7.2 and any simulator running iOS 8.x or greater worked fine.
Is it a xcode 7.3 bug?
Thanks,
Max
The issue is with OS X 10.11.4. Stay at OS X 10.11.3 or use the 10.11.5 beta.
Yes I got the same problem too after getting the latest Xcode 7.2 -> 7.3.
It looks like a problem with Apples background services crashing in the simulator and not telling its client i.e. the iCloud Drive or your app.
Even triggering an iCloud re-sync doesn't sort it so for the time being we have to debug on a real device which is a pain.
Looking in the system log via the simulator (Debug -> Open System Log), I see a lot of Sandbox (bird) access denied messages from the simulator which I guess are related to the issue - there is more info in some e.g.:
Process: bird [597]
Path: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/System/Library/PrivateFrameworks/CloudDocsDaemon.framework/bird
Load Address: 0x1085b8000
Identifier: bird
Version: ??? (???)
Code Type: x86_64 (Native)
Parent Process: launchd_sim [566]
User ID: 501
Date/Time: 2016-04-07 08:28:45.714 +0100
OS Version: Mac OS X 10.11.4 (15E65)
Report Version: 8
Thread 0:
0 libsystem_kernel.dylib 0x000000010aae21fa openbyid_np + 10
1 CloudDocsDaemon 0x00000001086f0664 -[BRCRelativePath _resolveAndKeepOpenMustExist:error:] + 872
etc.
I guess there are some permissions that have not been set on the file system that is used on the Mac backend for the simulator, but I've no idea how or what to change.
Do you get the same errors in your log when trying to use iCloud?
The only other thing I did recently was to install the latest Xamarin Studio, I hope that's not related but I doubt it.
Thanks
Matt

Meteor does not run - exit code 8 + unable to allocate arraybuffer

I am trying to run Meteor on my computer and it does not work.
I get the exit code 8 + another error about not being able to allocate arraybuffer.
The error details are way too long for me to put everything here...
Do you have any ideas how to solde it?
Thanks in advance

Phonegap IOS Running HiWorld Sample App Produces "EXC_BAD_ACCESS"

OSX: 10.6.8
Xcode: 4.0.2
Phonegap: 1.4.1.js or Cardova-1.7.0
Following simple HiWorld example http://phonegap.com/start produces the following error from:
AppDelegate.m:
self.viewCOntroller = [[[MainViewCOntroller alloc] init] autorelease];
ERROR:
Thread 1: Program received signal: "EXC_BAD_ACCESS"
EDIT: I was using the ipad 3.2 Simulator, as soon as I changed it to iphone 4.0 or above the problem went away.
This is (in my opinion), the most common error in iOs development.
The error means that you're trying to access something that has already been released.
You may be trying to access the viewController sometime after having already released it.
Remove autorelease and see what happens.

Resources