mTouch | mTouch移动端手势操作库，解决zepto库 “ 点透 ” 的bug，并支持事件委托

by DMQ JavaScript Version: Current License: No License

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

kandi X-RAY | mTouch Summary

mTouch is a JavaScript library. mTouch has no bugs, it has no vulnerabilities and it has low support. You can install using 'npm i mtouch-js' or download it from GitHub, npm.

mTouch移动端 ( 兼容pc端) 手势操作库，解决zepto库“点透”的bug，并支持事件委托.

Support

Quality

Security

License

Reuse

Support

mTouch has a low active ecosystem.

It has 67 star(s) with 35 fork(s). There are 9 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 7 have been closed. On average issues are closed in 54 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of mTouch is current.

Quality

mTouch has no bugs reported.

Security

mTouch has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

mTouch does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

mTouch releases are not available. You will need to build from source code and install.

Deployable package is available in npm.

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

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 mTouch

Get all kandi verified functions for this library.

mTouch Key Features

No Key Features are available at this moment for mTouch.

mTouch Examples and Code Snippets

No Code Snippets are available at this moment for mTouch.

Community Discussions

Trending Discussions on mTouch

Xamarin iOS Building Error: Unpack local framework faild

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

Xamarin ios submission error when submitting adhoc distribution to TestFlight

iOs App rejected by Apple - not getting the packages that uses UIWebview while using 'grep -r UIWebView'

Unable to Resolve Deprecation of UIWebView warning while uploading Xamarin application

Could not register the assembly System.ArgumentNullException: Value cannot be null - Problem with Visual Studio for Mac

Xamarin forms ios app rejected due to Deprecated API Usage UIWebView

Xamarin.iOS native linking error MTOUCH MT5210 undefined symbol std::string

Still getting ITMS-90809: Deprecated API Usage after using --optimize=force-rejected-types-removal

Xamarin iOS Firebase Native linking failed

QUESTION

Xamarin iOS Building Error: Unpack local framework faild

Asked 2021-May-26 at 10:57

I want to build a long time not used project. After updating all possible nuget packages and try to fix the most error on my own I got the following output:

...

ANSWER

Answered 2021-May-26 at 10:57

Problem solved by removing all nuget packages and reinstall it manual.

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

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

QUESTION

Xamarin ios submission error when submitting adhoc distribution to TestFlight

Asked 2020-Oct-21 at 12:21

So i have been trying to get past the following error after submitting my app to Apple TestFight:

...

ANSWER

Answered 2020-Oct-21 at 12:21

The problem here turned out to be the HockeySDK.Xamarin package i was using which is apparently now deprecated. Upon removing this dependency and replacing with AppCenter the submission was approved. I figured this out by sheer luck so i am concerned about being in a hopeless place again in future where apple denies my submission with little to no clue of how i can fix.

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

QUESTION

iOs App rejected by Apple - not getting the packages that uses UIWebview while using 'grep -r UIWebView'

Asked 2020-Sep-17 at 04:46

I am writing the full story, main issue is mentioned in the end.

Mail from Apple:

Link I have followed to fix this issue:Doc used to fix the issue

ios build page:

Visual studi version:

Xamarin iOs versions:

xamarin.forms version:4.6.0.1180

Webview Integration: I am using 'webview' in my Xamarin.forms project which is common for android and ios.

I have done a search by using the keyword: 'UIWebview', but I couldn't find any such usage in my project.

And then I have added --warn-on-type-ref=UIKit.UIWebView in mtouch argument. Warning log received in the build:

And then I was trying with grep -r UIWebView. I am not sure whether this is the right way to write the command in terminal. Help me if I am doing wrong. _/_

I am waiting for a long time.Why it's showing recursive search of stdin??How can I find out the packages which is using UIWebview in xamarin?

Can anyone help me to jump out of this issue . What may be the mistake I have done here ??????

Thnx in advance :)

...

ANSWER

Answered 2020-Sep-17 at 04:46

I have fixed the issue. There is a change in the way which I have tried 'grep -r UIWebView'

So for all the devprs who all are facing the same issue. I am posting the way in which I solved my issue.

delete bin and obj folders

Consider your project path is User/documents/xamarin/myproject

Then add cd documents cd xamarin

then write grep -lr "UIWebView" . and then return(mac)

You will receive an output that contains all the librraies that using UIWebview. Main issue will be the Hockeyapp sdk.You should replace it with app center. Delete or update the other libraries which are having UIWebview reference. And if you are getting sqlite3,just ignore it.

Create archeive file.Upload to app store. :)

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

QUESTION

Unable to Resolve Deprecation of UIWebView warning while uploading Xamarin application

Asked 2020-Sep-15 at 13:22

I Have followed the blog https://devblogs.microsoft.com/xamarin/uiwebview-deprecation-xamarin-forms/ to remove the UIWebView dependency in my project.

According to the document

1)xamarin.forms version is 4.6 2)xamarin.ios version is 13.20 3)I added the command in mtouch Arguments and linker is link All

I still got warning while upoading build to test flight

I then followed this document https://docs.microsoft.com/en-us/xamarin/ios/release-notes/13/13.16#help-with-uiwebview-deprecation where we can find out whether UIWebView is still being used in our application.I am getting below in the build output.

...

ANSWER

Answered 2020-Sep-09 at 17:31

Please follow this link

simply go to your iOS project, open the project properties and add this flag in the 'additional mtouch arguments field: --optimize=experimental-xforms-product-type' in your

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

QUESTION

Could not register the assembly System.ArgumentNullException: Value cannot be null - Problem with Visual Studio for Mac

Asked 2020-Aug-24 at 08:39

I have a problem building a project by error: Could not register the assembly 'Xamarin.Essentials': System.ArgumentNullException: Value cannot be null.

Xamarin.Essential is NuGet Package: Xamarin.Essential Nuget Gallery

I did all the recommended cleaning on VS and it still doesn't work. Anyone had a similar problem?

Visual Studio for Mac - version 8.6.5 (build 23)

Xamarin.Essentials - version 1.5.3.2

Error Visual Studio description: /Users/.../App.iOS/MTOUCH: Error MT4116: Could not register the assembly 'Xamarin.Essentials': System.ArgumentNullException: Value cannot be null. (MT4116) (App.iOS)

...

ANSWER

Answered 2020-Jul-13 at 09:55

Could not register the assembly 'Xamarin.Essentials': System.ArgumentNullException: Value cannot be null

1) close VS for Mac, delete all nuget caches under ~/.nuget/packages, ~/.local/share/NuGet/v3-cache and ~/.local/share/NuGet/plugins-cache

2) delete the whole bin and obj folder under the project folder and then restart your project again.

3) try to uninstall that Xamarin.Essentials nuget package and reinstall that package in your project to test again.

Also, try the lower version 1.3.1.

4) you can also create a new project and then install that package to test whether the issue still persists in the new project.

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

QUESTION

Xamarin forms ios app rejected due to Deprecated API Usage UIWebView

Asked 2020-Jun-11 at 05:25

I have a xamarin.forms app which have a webview. Whenever I try to publish the app to apple app store I get the Deprecated API Usage UIWebView warning and my app gets rejected. I saw the issue raised in https://github.com/xamarin/Xamarin.Forms/issues/7323. But I could't fix my issue. I replaced the webView using this render.

...

ANSWER

Answered 2020-Jun-11 at 05:25

Couldn't post this as a comment, because I wanted to share a picture.

This happened to me before too, where I set --optimize=experimental-xforms-product-type but I still got that error.

My issue was that I set those additional mtouch arguments for the wrong configuration. As you can see in the image, make sure you are placing those values in the right configuration and platform! It should be the same combination that you use for creating the archive:

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

QUESTION

Xamarin.iOS native linking error MTOUCH MT5210 undefined symbol std::string

Asked 2020-May-28 at 23:26

My Xamarion.iOS binding project has the links to all the required native video SDK libraries and native OS frameworks. I have set the required frameworks using Frameworks attribute. Other settings include SmartLink=true, ForceLoad=true, IsCxx=true, LinkerFlags="-lc++". It can be built into a C# DLL. In iOS project, the DLL is referenced and used. However there are native linking errors.

MTOUCH: Error MT5210: Native linking failed, undefined symbol: std::string::_Rep::_M_destroy(std::allocator const&). Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.

The details in build log: Undefined symbols for architecture arm64: "std::string::_Rep::_M_destroy(std::allocator const&)", referenced from: HPR_UTF82A(char const*) in libHCCore.a(HPR_Utils.o) HPR_A2UTF8(char const*) in libHCCore.a(HPR_Utils.o) "std::string::_Rep::_S_empty_rep_storage", referenced from: HPR_UTF82A(char const*) in libHCCore.a(HPR_Utils.o) HPR_A2UTF8(char const*) in libHCCore.a(HPR_Utils.o) "std::string::assign(char const*, unsigned long)", referenced from: HPR_UTF82A(char const*) in libHCCore.a(HPR_Utils.o) HPR_A2UTF8(char const*) in libHCCore.a(HPR_Utils.o) "std::basic_string, std::allocator >::basic_string(char const*, std::allocator const&)", referenced from: HPR_A2UTF8(char const*) in libHCCore.a(HPR_Utils.o) "std::basic_string, std::allocator >::basic_string(std::string const&)", referenced from: HPR_A2UTF8(char const*) in libHCCore.a(HPR_Utils.o) ld: symbol(s) not found for architecture arm64 clang : error : linker command failed with exit code 1 (use -v to see invocation)

The wrap errors:

MTOUCH: Warning MT5215: References to 'System' might require additional -framework=XXX or -lXXX instructions to the native linker (MT5215)

Error MT5201: Native linking failed. Please review the build log and the user flags provided to gcc: -ObjC (MT5201)

MTOUCH: Error MT5202: Native linking failed. Please review the build log. (MT5202)

clang: Error: linker command failed with exit code 1 (use -v to see invocation)

Please shed light. Thanks.

No such native linking error in Xcode. The build settings:

...

ANSWER

Answered 2020-May-28 at 23:26

Managed linking and native linking may remove code. Link All may remove more code. So need to solve the problem instead of making the issues disappear using Link All. When using Link All, need to use Preserve attribute to preserve code.

I added all native references, set the linking options correctly. Also I set the linker flags to include all the required OS platform frameworks correctly. What I really missed was a native dynamic framework which needs to be added as a reference. Then instead of getting undefined symbols, I got duplicate symbols. I had to remove a reference to a native library.

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

QUESTION

Still getting ITMS-90809: Deprecated API Usage after using --optimize=force-rejected-types-removal

Asked 2020-May-25 at 15:09

This has been killing me for the last couple of days. I have read everything I can find on this error and have done what xamarin says but it still doesn't work.

I can't get my builds to get through azure pipeline xamarin.ios build and deploy to apple.

When I build locally I get messages like

...

ANSWER

Answered 2020-May-04 at 14:06

I just got my build to pass Apple's inspection.

What ended up working for me was building locally and packaging the ipa file. On my mac I then changed the ipa extension to zip and unzipped it. I used terminal to go to the YOURAPPNAME.app "folder" and used grep -r UIWebView . to search for references. Don't forget the . so it searches the current directory. I missed that at first and got some message that grep was listening on stdin.

For me that resulted in a line like this: Binary file ./Frameworks/PersonalizedAdConsent.framework/PersonalizedAdConsent matches

Now, the important thing to note is the linker never warned about this, so I was completely unaware of it. In my case it was part of Firebase/Admob. I was only one release behind and updating to the latest fixed my problem.

I still am using --optimize=force-rejected-types-removal --warn-on-type-ref=UIKit.UIWebView -warnaserror:1503 as my mtouch args. But builds now get through.

I hope this helps point you guys in the right direction, I've spent the last 3 days just trying to get builds to upload reading every post I could find on the web on this problem.

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

QUESTION

Xamarin iOS Firebase Native linking failed

Asked 2020-May-24 at 17:15

After updating the Firebase libraries, I'm getting the following errors:

MTOUCH : error MT5210: Native linking failed, undefined symbol: _APMAnalyticsConfiguration. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. Blockquote

MTOUCH : error MT5210: Native linking failed, undefined symbol: _APMAppMeasurementOriginFirebase. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.

MTOUCH : error MT5210: Native linking failed, undefined symbol: _APMIsAnalyticsCollectionDeactivated. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.

MTOUCH : error MT5210: Native linking failed, undefined symbol: _APMIsAnalyticsCollectionEnabled. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.

MTOUCH : error MT5210: Native linking failed, undefined symbol: _APMMonitorLogTagOptionKey. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.

MTOUCH : error MT5210: Native linking failed, undefined symbol: _APMSafelistedEventsOptionKey. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.

I've tried the following:

Deleting obj and bin folders
Cleaning the project
Initializing Firebase core (Firebase.Core.App.Configure();)

I've tried all linker behavior options.

I'm referencing the following Firebase libraries:

Xamarin.Firebase.iOS.Analytics (6.4.1)
Xamarin.Firebase.iOS.CloudMessaging (4.3.0)
Xamarin.Firebase.iOS.Core (6.6.6)
Xamarin.Firebase.iOS.DynamicLinks (4.0.8)
Xamarin.Firebase.iOS.Installations (1.1.1)
Xamarin.Firebase.iOS.InstanceId (4.3.3)

Does anyone know how to solve this?

...

ANSWER

Answered 2020-May-24 at 17:15

Unfortunately, there isn't much that you can do in this case. The error is related to incorrect linking. The guys from Xamarin have messed up the bindings after one of the upgrades. You can read more about using native libraries in Xamarin here & more specifically here.

However, you can still do something to help - isolate which package caused the issue and from which version onwards it happens. Then, report it at the official GitHub repository for Google APIs here.

P.S. I have gone through the issues and haven't seen this exact list of errors. There have been (and still are) a lot of binding issues, which are waiting to be fixed. So, in order to speed things up, discuss it with the devs from the issue and hopefully, they will be able to resolve it quickly.

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

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

Vulnerabilities

No vulnerabilities reported

Install mTouch

You can install using 'npm i mtouch-js' or download it from GitHub, npm.

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: