it's been weeks that I'm blocked because I can't build my project in Xcode on iOS. I looked all over the internet, none of the suggestions worked for me. I really hope I'm not a rare exception because this problem is painful and prevents me from moving forward..
Here is a the error that i have in Xcode
"#import <AppLovinSDK/AppLovinSDK.h' file not found"
Try to Build from Unity and not Build and Run:
And then open the .xworkspace file and not the .xcodeproj file:
I encountered it yesterday. If ApplovinSDK in Podfile is added implicitly, try to make it explicit. The problem was solved in my case.
I describe the detail..
There was no AppLovinSDK in the Podfile.
The Podfile had "GoogleMobileAdsMediationAppLovin" instead.
ApplovinSDK will be installed from it.
I tried to add ApplovinSDK in Podfile ahead of "GoogleMobileAdsMediationAppLovin"
Then it works.
like this...
pod 'ApplovinSDK', '10.3.6' --- Added.
pod 'GoogleMobileAdsMediationAppLovin', '10.3.6.0'
I hope it helps.
Related
I have been stuck here for quite a while.
I know this is pretty basic, but plss help me out on this one.
I am familiar with Visual Studio for quite some time. So decided to give VS Code a shot.
I wanted to compile and run a simple 'Hello World' program in C#.[ref. Brackeys(Youtube)]
I have followed all the steps, but when I type in the cmd "dotnet run"
Failed to create CoreCLR, HRESULT: 0x80070057
This is what happens.
Are there any steps missing? Or some installation error, or I am missing some steps?
I am running this on :
Windows 10 [x64]
dotnet-sdk-3.1.402-win-x64
VSCodeUserSetup-x64-1.49.2
[
I think you've found a bug in the .NET SDK. It doesn't appear to like the folder name for the project being ;).
If I have it in #Code it runs fine. If I put it in #Code\;) then it fails with the same error.
I've opened an issue here: https://github.com/dotnet/sdk/issues/13954
The offending character is actually the ; (semicolon) character in your path. I had a similar issue, and once I renamed the path, my solution ran fine. Also note that having the ^ character (caret) can cause different issues in Visual Studio. Beyond those two, the path can contain any special character other than \/:*?"<>| which are prohibited by Windows.
I've been trying to run a UI test via Visual Studio Mobile center for a while now, but I'm getting the following error:
Preparing tests... failed.
Error: Cannot prepare UI Test artifacts. Returning exit code 20.
I looked on the mobile-center-cli github page and found that error codes 1 until 63 are reserved for TestCloud. There is really no documentation about this error so I hope someone is able to point me into the right direction.
Command used:
mobile-center test run uitest --app "MyAppName" --devices d5c95903 --app-path "pathToApk" --test-series "master" --locale "en_US" --build-dir "PathToBinRelease"
It sounds like you may be specifying the wrong folder for your --build-dir.
The --build-dir should be the bin/Debug folder of your Xamarin.UITest project, something like this:
"/Users/User/AppSolution/App.UITests/bin/Debug"
Can you please try the above and let me know if it resolves the issue?
Glenn
Another reason for this error is if there is more than one version of Xamarin.UITest present in the packages folder, that is visible in the root of your project.
Remove the unnecessary versions of Xamarin.UITest and give it another go.
I had this error. I added this param to my script:
--uitest-tools-dir "...your_path\packages\Xamarin.UITest.2.0.10\tools"
This is work for me.
--uitest-tools-dir $APPCENTER_SOURCE_DIRECTORY/packages/Xamarin.UITest.*/tools
https://tomsoderling.github.io/AppCenter-Automated-UI-tests-on-build/
Built this game through Unity, and managed to compile through xCode once before. Without any apparent changes, however, this error message turns up. I don't understand where to start looking for a fix, but maybe someone else have a clue? I've seen similar looking errors through searches, though the fixes seem arbitrary compared to mine.
Anyone able to shed some light? Thank you!!
0 0x1034de0e7 __assert_rtn + 144
1 0x10351350c archive::File<arm>::makeObjectFileForMember(archive::File<arm>::Entry const*) const + 1142
2 0x103512c9a archive::File<arm>::forEachAtom(ld::File::AtomHandler&) const + 416
3 0x10352a6a1 ld::tool::InputFiles::forEachInitialAtom(ld::File::AtomHandler&, ld::Internal&) + 465
4 0x10353490e ld::tool::Resolver::resolve() + 48
5 0x1034dec47 main + 679
A linker snapshot was created at:
/tmp/wingOstar-2014-09-26-171939.ld-snapshot
ld: Assertion failed: (memberIndex != 0), function makeObjectFileForMember, file /SourceCache/ld64/ld64-236.4/src/ld/parsers/archive_file.cpp, line 355.
clang: error: linker command failed with exit code 1 (use -v to see invocation)
This seems like the kid of error the Xcode developers hope you never actually see...
The part of that message that is likely most useful for searching against will be the ld: Assertion failed: (memberIndex != 0), since that is the root of the error rather than supporting information.
I probably found the same few sources you did, but they indicated that this is caused by corruption in one of the resources Xcode is trying to link your program against, rather than something immediately caused by your own code. A file becoming corrupted by some external action would explain how this can happen despite no obvious changes in your program source.
So the obvious suggestion for fixing this would be to repair the corruption by making sure whatever is causing it gets recompiled. The first thing to do is to completely clean your project so that no older precompiled files are used and all of your own code is rebuilt. Since your error mentions a source cache, follow the recommendation here to wipe all caches, not just those cleared by the Product->Clean option.
The error message also gives a suggestion to use the -v flag to see what ld is actually doing, which may help you narrow down which object files could be corrupt (by showing you which ones are actually used). To add the flag, go to Build Settings in your project's settings, go down to Linking->Other linker flags, and add -v to those. Once you've rebuilt the project, look at the Build messages in the Report Navigator panel, and expand the linker messages for a full list of linked objects. If any of these options refer to libraries you provided, consider deleting and rebuilding them, before cleaning and rebuilding your project again.
I have a program that interfacing SWI-Prolog in Visual Studio. Previously, I used VS2010 (XP) and everything works fine. Then I upgrade my VS to become VS2012 (Win7) and now I have a problem in my code.
When it comes to the following code:
PlEngine.Initialize(param);
it always gives me the following exception message:
The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Can anybody spot what mistake that I made or if possible some modification that I have to do, due to the upgrading process?
Additional information regarding my code:
I used the most updated swiPLCs library (version: 1.1.60301.0)
my 'param' in my code above is: string[] param = { "-q", "-f", #"c:\program files (x86)\pl\"};
I have set the path environment variable to: c:\program files (x86)\pl\ and c:\program files (x86)\pl\bin
I have this setting in my code: Environment.SetEnvironmentVariable("SWI_HOME_DIR", Global.g_prologLocation);
I had the reference to: swiPLcs.dll
I already tried to use the SWIProlog 64 bit, but I still have the same problem
Any help is really appreciated.
Many thanks
I finally got the answer myself.
Unlike VS2010, In VS2012 it seems that you have to add SWI-Prolog package into VS2012.
So add SWI.Prolog package using Nuget.
How?
See: https://nuget.org/packages/SWI.Prolog
And VS2012 will recognize the SWI.Prolog now.
Thanks anyway
I downloaded the latest MonoTouch (4.0.4.1 and MonoDevelop 2.6 beta) to fix some issues we were having.
I was hoping that my build in Jenkins (using mdtool) would start working, but no luck.
mdtool gives this error (shortened):
2011-07-28 08:18:47.399 mdtool[14484:60f] *** __NSAutoreleaseNoPool(): Object 0x492260 of class NSCFString autoreleased with no pool in place - just leaking
2011-07-28 08:18:47.401 mdtool[14484:60f] +[NSDictionary dictionaryWithContentsOfFile:]: unrecognized selector sent to class 0xa0bdd3ec
2011-07-28 08:18:47.401 mdtool[14484:60f] *** __NSAutoreleaseNoPool(): Object 0x3f02540 of class NSCFString autoreleased with no pool in place - just leaking
In the past this was related to code generation with the designer.
Is this a known issue being working on by Xamarin? (I can open a bugzilla bug if needed)
PS: one thing else to mention, is we have deleted the designer.cs files for several of our views. (This was a crude way to disable code generation at the time, we needed to manually setup our outlets, exports, etc.)
EDIT: posted to bugzilla here.
You are not using the stable version of MonoDevelop, you are using an outdated preview, that was fixed in later betas.