Tag Archives: ios

Xcode debugging for the real iPhone Error: code signature version is no longer supported

Details

Unable to install "MyApp"
Domain: com.apple.dt.MobileDeviceErrorDomain
Code: -402620375
-

The code signature version is no longer supported.
Domain: com.apple.dt.MobileDeviceErrorDomain
Code: -402620375
User Info: {
  DVTRadarComponentKey = 261622;
  MobileDeviceErrorCode = "(0xE8008029)";
  "com.apple.dtdevicekit.stacktrace" = (
0  DTDeviceKitBase           0x000000011edd83b8 DTDKCreateNSErrorFromAMDErrorCode + 220
1  DTDeviceKitBase           0x000000011ee16ae1 __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 155
2  DVTFoundation            0x0000000107881b7c DVTInvokeWithStrongOwnership + 71
3  DTDeviceKitBase           0x000000011ee16822 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1440
4  IDEiOSSupportCore          0x000000011eccf999 __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.294 + 3534
5  DVTFoundation            0x00000001079b4931 __DVT_CALLING_CLIENT_BLOCK__ + 7
6  DVTFoundation            0x00000001079b655b __DVTDispatchAsync_block_invoke + 1191
7  libdispatch.dylib          0x00007fff20508603 _dispatch_call_block_and_release + 12
8  libdispatch.dylib          0x00007fff205097e6 _dispatch_client_callout + 8
9  libdispatch.dylib          0x00007fff2050f5ca _dispatch_lane_serial_drain + 606
10 libdispatch.dylib          0x00007fff2051008d _dispatch_lane_invoke + 366
11 libdispatch.dylib          0x00007fff20519bed _dispatch_workloop_worker_thread + 811
12 libsystem_pthread.dylib       0x00007fff206b04c0 _pthread_wqthread + 314
13 libsystem_pthread.dylib       0x00007fff206af493 start_wqthread + 15
);
}
-

It may be caused by inconsistent signatures on the framework, such as do not embed , and embed and sign

Possible solutions:
app targets -> General -> Frameworks,Libraries,and EmbeddedContent -> Modify embed and sign to do not embed .

How to Solve pod Error: “Authentication token is invalid or unverified. Either verify it with the email that…”

The following error occurs when executing pod trunk push:

[!] Authentication token is invalid or unverified. Either verify it with the email that was sent or register a new session.

Solution:

1. Execute the command: pod trunk register ‘your mailbox’, ‘XXXXXX’ — description =’xxxx ‘   Re register your account
2. Find and open the verification link in your email
3. Return to the terminal and execute the command again: pod trunk push xxxxx.podspec — allow warnings

Sending ‘const NSString *’ to parameter of type ‘NSString *’ discards qualifiers [Solved]

For example, write const NSString* firstString = @"xxx";
NSString* secondString = @"yyyy";
[secondString isEqualToString:firstString];
There is a warning about sending 'const NSString *' to parameter of type 'NSString *' discards qualifiers.
Workaround.
Change const NSString* firstString = @"xxx";
to NSString* const firstString = @"xxx";

Explanation: The former is equivalent to the pointer itself is not modifiable, the latter indicates that the content pointed to by the pointer is not modifiable, both serve to make firstString readable and unwritable only.

 

Sending ‘const NSString *__strong‘ to parameter of type ‘NSString *‘ discards qualifiers

String value encountered a warning message, record it

Sending 'const NSString *__strong' to parameter of type 'NSString *' discards qualifiers

The code is written like this

UIKIT_EXTERN const NSString * kNetworkType;

This warning will be issued when using it, and it will be changed to:

UIKIT_EXTERN NSString * const kNetworkType;

If const is placed after nsstring *, there will be no warning.

Could not find module ‘xxxxxxx‘ for target ‘arm64-apple-ios-simulator‘;

Xcode12 simulator compilation error

After upgrading Xcode to 12.0.1, the following error occurred in simulator compilation
Could not find module ‘xxxxxxx’ for target ‘arm64-apple-ios-simulator’; found: x86_ 64-apple-ios-simulator, x86_ 64
many methods have been found on the Internet, but they can’t be solved. Later, they have been solved through research. Here’s a record

First of all, make clear the concept

There is an architecture option in

    Xcode, and its value is standard architectures – $(arcs)_ Standard) is (armv7 and arm64) in real machine compilation, and (x86) in simulator compilation_ If the build active architectures only option in Xcode is yes, it means that only the current architecture will be compiled. For real computers, it is generally arm64, and the emulator is usually x86_ 64. If it is no, it means that the supported architectures are compiled at the same time. The exclusive architectures option in Xcode of the above architectures means that the excluded architectures are filled in here. Therefore, if arm64 is used here, it means that you do not want to compile the valid in Xcode_ As for the arcs option, it’s the current effective architecture (I’m also dizzy. Apple is so complicated that it needs this when it has 1). Generally, the value filled in here is the same as 1

    So here comes the question…. The problem I encountered was that I filled in arm64 arm64e in 4, so the compiler simulator kept reporting errors, and then changed all kinds of things, including the architecture of the third Library in pods.

    Solution
    although Standard Architecture (x86) is set in 1_ However, the effective architecture in 4 is arm64, arm64e, so only arm64 can be used for the simulator. (it is said that the simulator of xcode12 supports arm64, but my computer is i5, so this one doesn’t use arm64). So the module he compiled is for ‘arm64 Apple IOS simulator’, but the simulator is found: x86_ 64-apple-ios-simulator。 So I made a mistake if you encounter the same type of mistakes, you can think clearly about the relationship between 1, 2, 3 and 4.

    Pod component

    post_install do |installer|
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            if config.name == 'Debug'
              config.build_settings["VALID_ARCHS"] = "arm64 arm64e x86_64 i386"
            else
              config.build_settings["VALID_ARCHS"] = "arm64 arm64e"
            end
        end
    end
    end
    

    Finally, the project clean recompile, OK

[app] install and compile libimobililedevice, How to solve the error

Problem Description:

Error: Failure while executing; `tar --extract --no-same-owner --file /Users/xmly/Library/Caches/Homebrew/downloads/58f1d108442b2cdceb8e86e7d05328381fd0a85b67ae46a66fa710f8f1786b02--libtasn1-4.16.0_1.big_sur.bottle.tar.gz --directory /private/tmp/d20210629-40261-ibafl5` exited with 1. Here's the output:
tar: Error opening archive: Failed to open '/Users/xmly/Library/Caches/Homebrew/downloads/58f1d108442b2cdceb8e86e7d05328381fd0a85b67ae46a66fa710f8f1786b02--libtasn1-4.16.0_1.big_sur.bottle.tar.gz'

Cause of the problem:

Maybe some of the dependent libraries were not downloaded
later, after the installation environment was prepared, they succeeded


* brew install build-essential automake autoconf git cmake pkg-config libtool

install

* Method 1:
	git clone https://github.com/libimobiledevice/libimobiledevice.git
	cd libimobiledevice
	./autogen.sh
	make
	sudo make install

* Method 2:
	brew install --HADE libmobliedevice
	# If you do not add - HADE installation is an older version, does not support IOS 10 or above

It is invalid to submit the content directly after pasting it on the mobile terminal of Vue HTML5 editor

Modify the source code vue-html5-editor.js
Directory:

open this file, search for contenteditable, add id = “container”

and then search for Keyup
comment code

 // content.addEventListener('keyup', function () {
 //     this$1.$emit('change', content.innerHTML);
 //     this$1.saveCurrentRange();
 // }, false);

Add code

const handleListenChange = (mutationsList, observer) => {
 this$1.$emit('change', content.innerHTML);
 this$1.saveCurrentRange();
}
const mutationObserver = new MutationObserver(handleListenChange)
const element = document.querySelector('#container')
const options = {
 attributes: true,
 childList: true,
 subtree: true,
 characterData: true
}

It’s like this on the whole

I’ve looked at others and modified it myself. This question is more detailed than that of the blogger. Link to attach. If you have any other questions, take a look
CSDN of Dashen

The solution of MAC OpenSSL is not available

Mac OpenSSL not found/loading failed

OpenSSL is a secure socket layer cipher library, including the main cryptographic algorithms, commonly used key and certificate encapsulation management functions and SSL protocol, and provides a wealth of applications for testing or other purposes.

Mac OSX install new OpenSSL

Currently, Mac OSX can install the specified version of OpenSSL through brew.

Confirm the version and location of the installed OpenSSL

$ which openssl

Determine version

$ openssl version

Brew install OpenSSL

$ brew install openssl

Brew update OpenSSL

$ brew upgrade openssl

Brew force link to OpenSSL

$ brew link openssl –force

The above is the introduction of updating OpenSSL under Mac to the latest version.

 
An error occurred when installing the software through homebrew or other ways

Error running ‘requirements_ osx_ brew_ libs_ install openssl’Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib (LoadError)

It may be caused by not installing or environment variable problems (you can judge by inputting OpenSSL command in the terminal and viewing feedback information)

1. You can solve this problem by re installing OpenSSL

Steps to re install OpenSSL:

Remove OpenSSL (other versions may exist in the removal method. It is recommended to uninstall all versions through uninstall)

brew remove openssl

Uninstall all versions of OpenSSL

brew uninstall –force openssl

Install OpenSSL

brew install openssl

Configure environment variables

echo ‘export PATH=”/usr/local/opt/openssl/bin:$PATH”‘ >& gt; ~/. bash_ profile

 

IOS app connect error store submitted for review

Recently, an error was reported when submitting the audit package: app store connect operation error.

You must be an Admin or Technical user in order to deliver content or metada.(1070)

Screenshot of error report:

 

Solution: use the transporter tool to upload, once OK. (I tried other methods in the middle, but I won’t talk about them one by one. I successfully uploaded this method, and the transporter tool can be found in the app store. Good luck to you.).