-
Notifications
You must be signed in to change notification settings - Fork 569
[BUG] libSkiaSharp.framework.dSYM missing #3110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Also facing this message when submitting an .ipa to AppStore |
Has any thing been done about this issue I am blocked |
I am blocked as well, any updates? |
Same here. |
1 similar comment
Same here. |
there is no support do we have to use it? |
I am having a look at a way to publish the symbols as part of the framework that is included in the app. Hopefully this makes life much easier for everyone. One thing I have to check is if Apple is actually blocking the uploads witout symbols? Is it just the skia symbols missing, or are the app symbols missing too? |
As far as I can tell, its just the skia symbols. I haven't had the issue with anything else. |
From my experience, it is not a blocker, since Apple is accepting the build - however there always the warning. @mattleibow It is just the Skia symbols For reference I'm using these packages:
|
OK, that is good to know. I think I got the symbols in the packages so hopefully once #3184 finishes building you can test the artifacts? I am switching to the different xcframework format which can contain the debug symbols and the release binaries. Should not make much of a difference to the app as the build process does the extraction and everything, but it is not 100% the same as before. Let me know if you are able to test the packages! |
@mattleibow can you tell me how to do it? No promises of when, since I'm going on a business trip, but whenever possible I can try it out. |
do we have a new nuget package? |
To test, download the nuget artifact from https://dev.azure.com/xamarin/6fd3d886-57a5-4e31-8db7-52a1b47c07a8/_build/results?buildId=136992 Extract to a folder and then add that folder as a nuget source in VS or in a nuget.config: <?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="nuget-skia-pr" value="/path/to/nuget/folder" />
</packageSources>
</configuration> |
I am desperate to launch my app when is the final fix going to be available please . I am blocked. Do I have to use it ? is there an alternative? |
Are you not able to publish at all? Can you send a screenshot of the errors?
|
Unfortunately we are not able to use preview version at present. When is the fix going to be released ? any idea? Thanks for the help |
If you are using the latest stable, is apple blogging you or warning you? Can you share your error message or screenshot. |
Ok There is a new nuget released I will try it and let you know |
heh @mattleibow ! I've just got the latest off nuget. Get the same issue here, blocked in validation from Apple Any work around? any fix expected soon? Thanks |
Same issue that we started getting recently. Its not blocking just warnings. |
Description
When I create an ipa file it does not include the libSkiaSharp.framework.dSYM symbols
Code
The best way to share code for larger projects is a link to a GitHub repository: https://github.com/user/repo/tree/bug-123
But, you can also share a short block of code here:
// some C# code here
You can also share some XAML:
<!-- xaml code here -->
Expected Behavior
I expected it to be either generated by visual studio and tried several configurations to no avail and also I would have expected the symbols file would be part of the nuget packages for the platoforms
Actual Behavior
no symbols available in the build output
Version of SkiaSharp
3.116.0 (Current)
Last Known Good Version of SkiaSharp
2.88.9 (Previous)
IDE / Editor
Visual Studio (Windows)
Platform / Operating System
Android, iOS, Windows
Platform / Operating System Version
Windows 11
Devices
windows 11 pc
Relevant Screenshots
No response
Relevant Log Output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: