Xam.Plugins.ImageCropper | Xam | Form library

by XAM-Consulting C# Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | Xam.Plugins.ImageCropper Summary

Xam.Plugins.ImageCropper is a C# library typically used in User Interface, Form, Xamarin applications. Xam.Plugins.ImageCropper has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Xam.Plugins.ImageCropper is a useful image cropping and rotating library for Xamarin.iOS and Xamarin.Android.

Support

Quality

Security

License

Reuse

Support

Xam.Plugins.ImageCropper has a low active ecosystem.

It has 53 star(s) with 22 fork(s). There are 6 watchers for this library.

It had no major release in the last 6 months.

There are 8 open issues and 10 have been closed. On average issues are closed in 89 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Xam.Plugins.ImageCropper is current.

Quality

Xam.Plugins.ImageCropper has 0 bugs and 0 code smells.

Security

Xam.Plugins.ImageCropper has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Xam.Plugins.ImageCropper code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Xam.Plugins.ImageCropper is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

Xam.Plugins.ImageCropper releases are not available. You will need to build from source code and install.

Installation instructions are available. Examples and code snippets are not available.

Xam.Plugins.ImageCropper saves you 11 person hours of effort in developing the same functionality from scratch.

It has 32 lines of code, 0 functions and 20 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Xam.Plugins.ImageCropper

Get all kandi verified functions for this library.

Xam.Plugins.ImageCropper Key Features

No Key Features are available at this moment for Xam.Plugins.ImageCropper.

Xam.Plugins.ImageCropper Examples and Code Snippets

No Code Snippets are available at this moment for Xam.Plugins.ImageCropper.

Community Discussions

Trending Discussions on Xam.Plugins.ImageCropper

Getting 'ITMS-90338: Non-public API usage' and 'ITMS-90809: Deprecated API Usage' upon submitting Xamarin iOS to Apple AppStoreConnect TestFlight

QUESTION

Getting 'ITMS-90338: Non-public API usage' and 'ITMS-90809: Deprecated API Usage' upon submitting Xamarin iOS to Apple AppStoreConnect TestFlight

Asked 2021-Feb-10 at 10:55

We're receiving the following message upon submitting our Xamarin.Forms iOS app to Apple's TestFlight.

the Message:

Dear Developer,

We identified one or more issues with a recent delivery for your app, "[bundle name]" [bundle version] ([bundle version]). Please correct the following issues, then upload again.

ITMS-90338: Non-public API usage - The app references non-public selectors in [project name]: applicationWillTerminate, fontWeight, newSocketQueueForConnectionFromAddress:onSocket:, setOrientation:animated:, socket:didConnectToHost:port:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidSecure:, terminateWithSuccess. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).

Best regards,

The App Store Team

I have looked up the messages and made too many attempts to no avail. I'd appreciate it if someone could help having Apple to accept our submission.

Let me share more details about

the Environment:

This is a Xamarin.Forms app that we build using Azure DevOps's build pipelines (specifically, Xamarin.iOS task version 2.*) and release using Azure DevOps's release pipelines. We release that to Microsoft AppCenter and we then download the *.ipa from there. We submit it to Apple's AppStoreConnect TestFlight using Transporter app on the Mac from Apple's AppStore.

...

ANSWER

Answered 2021-Feb-10 at 02:23

There are two reasons why Apple reject this submitted version.

ITMS-90338: Non-public API usage - The app references non-public selectors in [project name]: applicationWillTerminate, fontWeight, newSocketQueueForConnectionFromAddress:onSocket:, setOrientation:animated:, socket:didConnectToHost:port:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidSecure:, terminateWithSuccess.

This means that you need to modify the list names of methods with another name, because these names will conflict with the private method names of Apple's system. You need to find them and replace them with other names.

ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability.

Starting in April 2020, Apple will reject apps that still use the deprecated UIWebView API. While Xamarin.Forms has switched to WKWebView as the default, there is still a reference to the older SDK in the Xamarin.Forms binaries. Current iOS linker behavior does not remove this, and as a result the deprecated UIWebView API will still appear to be referenced from your app when you submit to the App Store.

A preview version of the linker is available to fix this issue. To enable the preview, you will need to supply an additional argument --optimize=experimental-xforms-product-type to the linker.

Detailed steps can refer to UIWebView Deprecation and Xamarin.Forms.

Source https://stackoverflow.com/questions/66119480

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Xam.Plugins.ImageCropper

You can build these binding libraries by your self. For iOS, run make in iOS/extern, then build iOS project. For Android, download the lastest .aar and import the package into Android project, make sure you have installed JDK 1.8 and Android SDK 25.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: