Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 02 2016 16:31
    @chamons banned @IfErrThrowBrick_twitter
Rolf Bjarne Kvinge
@rolfbjarne
yeah, the page doesn't exist yet
Raimo
@Digifais
Aha okay, thanks!
Aimoré Sá Costa
@aimore
after doing
cd tests/tom-swifty-test make
Got the following error
"/Users/aimoresa/Downloads/binding-tools-for-swift/tests/tom-swifty-test/tom-swifty-test.csproj" (default target) (1) ->
"/Users/aimoresa/Downloads/binding-tools-for-swift/tom-swifty/tom-swifty.csproj" (default target) (4:2) ->
(BeforeBuild target) ->
/Users/aimoresa/Downloads/binding-tools-for-swift/tom-swifty/tom-swifty.csproj(63,5): error MSB3073: The command "make -C .. Constants.cs" exited with code 2.


"/Users/aimoresa/Downloads/binding-tools-for-swift/tests/tom-swifty-test/tom-swifty-test.csproj" (default target) (1) ->
"/Users/aimoresa/Downloads/binding-tools-for-swift/SwiftRuntimeLibrary.Mac/SwiftRuntimeLibrary.Mac.csproj" (default target) (5:2) ->
(GeneratedCSCode target) ->
/Users/aimoresa/Downloads/binding-tools-for-swift/SwiftRuntimeLibrary.Mac/SwiftRuntimeLibrary.Mac.csproj(288,5): error MSB3073: The command "/Library/Frameworks/Mono.framework/Versions/Current/Commands/mono /Users/aimoresa/Downloads/binding-tools-for-swift/SwiftRuntimeLibrary.Mac/../type-o-matic/bin/Debug/type-o-matic.exe --swift-lib-path=/Users/aimoresa/Downloads/binding-tools-for-swift/SwiftRuntimeLibrary.Mac/../apple/build/Ninja-ReleaseAssert/swift-macosx-x86_64/lib/swift/ --platform=mac --xamglue-framework=/Users/aimoresa/Downloads/binding-tools-for-swift/SwiftRuntimeLibrary.Mac/../swiftglue/bin/Debug/mac/FinalProduct/XamGlue.framework --output=GeneratedCode/BindingMetadata.MacOS.cs" exited with code 1.
Aimoré Sá Costa
@aimore
Rolf Bjarne Kvinge
@rolfbjarne
what happens if you run make in the top-level directory?
Aimoré Sá Costa
@aimore
you mean in binding-tools-for-swift
cd binding-tools-for-swift
make
it works
tom-swifty-test
does not
Dorta
@rdorta
Hello there... After updating to Xamarin.IOS 13.10.0.17 and Xcode 11.3.1, our app started failing to start with the message: dyld: symbol '_mono_interp_callbacks_pointer' not found. Any ideas on the cause of the issue? It works fine in previous version of Xcode/VS/Xamarin.iOS
Rolf Bjarne Kvinge
@rolfbjarne
that sounds like a bug
Dorta
@rdorta
Sure can.
Dorta
@rdorta
I might have some NDA issues with the build log. Any suggestion?
Sebastien Pouliot
@spouliot
do a Find and Replace on what you think is confidential, replace anything with [Redacted]
Dorta
@rdorta
Sebastien Pouliot
@spouliot
if you remember which previous versions you were using please add this to the report too :smile:
also since it crashed at startup you should have a crash report that you can attach
Dorta
@rdorta
It's a dylib issue, so it doesn't even generate a crash report. At least I never was able to find it on Xcode device panel
I have seem similar issues when working with different native bindings of swift libraries, that had different swift versions
But never saw it happen with a Mono dylib
Sebastien Pouliot
@spouliot
hmm… it should report (under dynamic linker daemon) but that’s generally not for missing symbols
Dorta
@rdorta
As for the version unfortunately I don't remember exactly what my version was, but have tested with 2 different previous versions of both Xcode anda Xamarin.iOS and its working
Ill triple check for the crash logs
Sebastien Pouliot
@spouliot
please add the version you tried - it’s helpful
also add the device console logs, it will show useful stuff (less than a crash report but better than nothing)
Dorta
@rdorta
Sure. It will be there in a min
Sebastien Pouliot
@spouliot
thanks :smile:
Dorta
@rdorta
Updated with crash log and 2 dev environments that works
Sebastien Pouliot
@spouliot
one more ask, can you give us the build log with an additional -v -v -v -v ?
we need to see what options are used, they are in /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mtouch @/Users/ricardodorta/arctouch/[Redacted]/[Redacted].iOS/obj/iPhone/Debug/device-builds/iphone11.8-13.3/response-file.rsp but only shown if more verbosity is used
Dorta
@rdorta
sure, one sec
Dorta
@rdorta
Is there a way on VS for Mac to get the build output to a file?
The build with diagnostics is getting trimmed in VS for MAC output window
Rolf Bjarne Kvinge
@rolfbjarne
no, but you can build from the command line
msbuild path/to/my.sln /p:Platform=iPhone /verbosity:diagnostic
nor0x
@nor0x
Hi all 👋 as you are discussing issues after upgrading to Xamarin.iOS 13.10.0.17 and Xcode 11.3.1. I have an issue that's very likely related to this - build.log and visual studio information included
https://github.com/xamarin/xamarin-macios/issues/7715#issuecomment-576713201
Sebastien Pouliot
@spouliot
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Topten.RichTextKit, Version=0.1.118.0, Culture=neutral, PublicKeyToken=null' ---> Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Topten.RichTextKit, Version=0.1.118.0, Culture=neutral, PublicKeyToken=null'
your code (binary) refers to an assembly that is not found by the linker
it’s a potential runtime issue for the simulator (JIT) but it’s a compile time error (linker or AOT) for device builds
from the logs you can see it’s referenced from
Loaded assembly 'MorePath.Skia, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' from MyPath/MyProject/bin/Debug/netstandard2.0/MorePath.Skia.dll References: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' References: 'MorePath.Core, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' References: 'SkiaSharp, Version=1.68.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' References: 'Topten.RichTextKit, Version=0.1.118.0, Culture=neutral, PublicKeyToken=null'
Dorta
@rdorta
Added crash logs from a new build removing HotReload and the interpreter
Seems a different reason of crash, but I honestly could not read much from it
There is no error shown on Application Output, it doest even show the application was terminated :(
nor0x
@nor0x
@spouliot thank you very much, i should really get better at reading through these logs ;-)
Sebastien Pouliot
@spouliot
np, some time things are well hidden ;-)
Gareth Pym
@gonz01d

Hi, I'm trying to use Sharpie v3.4.47 with Cocoapods v1.7.0 (also tried latest 1.8.x) and I'm unable to run a sharpie pod init command e.g. sharpie pod init iOS AFNetworking without the command failing and eventually returning ** Searching for requested CocoaPods ... error: Failed to run pod list

Full output:

** Setting up CocoaPods master repo ...
   (this may take a while the first time)
Setting up CocoaPods master repo

CocoaPods 1.9.0.beta.2 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.9.0.beta.2

Setup completed
** Searching for requested CocoaPods ...
error: Failed to run pod list

Has anyone experienced and resolved similar or is able to pass on their known working version combinations so I can try downgrading ?

Alex Soto
@dalexsoto
Hello @gonz01d unfortunately using cocoapods from objective-sharpie is currently not completely supported, YMMV so I would recommend manually fetching the headers of AFNetworking and run sharpie against them
also you could search nuget IIRC someone already bound AFNetworking on the past
Gareth Pym
@gonz01d
Hey @dalexsoto I'm actually trying to bind a different lib but used AFNetworking as a known working pod example to see if it would work where my other cocoapod failed, to help prove sharpie was working ok itself.
Cheers for the heads up - I'll try going the manual route with the headers