Branch.io Deep linking not working on iOS 13+. It does not show pop-up to open application(Ionic 5, Capacitor) - branch.io

I have added deep-linking integration in our app and using plugin capacitor-branch-deep-links. It is working till iOS 12.1 but in iOS 13+ it does not show a pop-up to open the application on a click of deep-link.
I have also tried forced uri redirect mode but none of these solutions are working.
https://help.branch.io/using-branch/docs/creating-a-deep-link#forced-redirections
Installed Dependencies:
Ionic 5.26.0
#capacitor/cli 2.4.5
#capacitor/core 2.4.5
#capacitor/ios 2.4.5
capacitor-branch-deep-links 3.0.0

After going through this link, I figured out that I was using the wrong Apple App Prefix and invalid Provisioning Profile Specifier. This correction fixed my issue. Though I am still not sure why it was working in iOS 12 with the wrong Apple App Prefix and Provision Profile

Related

Android 12 crash latest react-native-track-player version

After updating app in android 12 and try to run app in android 12 device and simulator facing issue for crashing.
Here is issue.
androidx.media.session.MediaButtonReceiver: Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present'
Resolve
With use of android:exported="true" fixed issue for run app but service not start once player on in app. so again crash app.
Please check the Github for React-Native-Track-Player.
There is a Beta version for use with Android 12.
Following this question, anyone was able to patch the package to make it work on Android 12? Using a non-final version seems more buggy than just adapting the stable one.

How to use titanium inspector using titanium 5.2.2?

I am using Appcelerator titanium CLI to build ios app. I want to debug the app With Chrome DevTools but it seems like it's not compatible with the version which I have installed currently.
As per ti-inspector documentation, I have installed the node package by the below command.
npm install -g ti-inspector
So, When I tried this into my titanium project directory I am getting this response which is unexpected.
tn-inspector
Unexpected error: undefined
NOTE: titanium version - 5.2.2
Useful GitHub link: https://github.com/omorandi/TiInspector
Need help to understand or mitigate this issue. Thanks in advance!!!.
That repo is 5 years old and might not be compatible with the current SDK. You can use this instruction: https://docs.axway.com/bundle/Appcelerator_Studio_allOS_en/page/debugging_android_apps_with_3rd-party_tools.html to use the internal dev tools connection.

Apache Cordova: Difference between browser and www platform

If I type on my console:
cordova platform ls
I get the following list for platforms:
Installed platforms:
Available platforms:
android ~6.3.0
blackberry10 ~3.8.0 (deprecated)
browser ~5.0.0
ios ~4.5.1
osx ~4.0.1
ubuntu ~4.3.4 (deprecated)
webos ~3.7.0
windows ~5.0.0
www ^3.12.0
But I cannot understand the difference between www platform and browser platform. The both seem to me that serve the very same purpose: Run cordova apps via the web.
But on a second thought it may be something slightly different. What is the reason for the two platforms? As fas as I look on documentation it says-documents mostly mobile platforms such as:
Windows phone
iOs
Android
Blackberry 10
I don't think www is a valid platform and it shows up in the list of available platforms because of a bug somewhere in the cordova-cli.
If you have a look at the supported platforms of the latest docs there is no mention of www. I do not know where version 3.12.0 comes from exactly, but one thing related to cordova and this version I found is that the latest version of cordova-app-hello-world is 3.12.0. If it would be a valid platform there would also be a github repo for it which is not present. So I suggest you just use the browser platform.
It could show if you are using ionic, www is the ionic build for ionic serve

Error when uploading to iTunesConnect

I am using Application Loader to upload my .ipa files (created with Adobe AIR v18) to iTunesConnect.
It's been working fine for months, but today I received two new errors:
The u option must have a non-empty value.
The password must have a non-empty value.
Can anyone shed some light on the issue?
I upgraded to Xcode 7.1 and that solved the problem!
Note: Xcode 7.1 comes with Application Loader 3.3.
You have 2 solutions:
1) Update your Xcode to 7.1 (but since you are not coding natively, use the solution #2 below)
or
2) Download and use the Application Loader v3.1 (Download link: https://itunespartner.apple.com/en/apps/tools ) to submit your IPA
Apart from low-belly's answer you can try to use XCode's built-in upload feature. If you go to the Organizer, just click on Upload to App Store:
This solved the problem for me in XCode 7.0.1.
Xcode 7.1 was downloading too slow (more than 4GB) and the update failed every time, so for now I downloaded the Application Loader 3.1 from iTunes Connect and it worked fine.
To download it you login into iTunes Connect -> Resources and Help -> click on View Tools (under the title Other Resources at the bottom of the page) and there is the download link.
I got the same error last night. Fixed it by signing out of Application Loader (3.6) and logging back in.
I got the same error with Application Loader 3.2. Submitting with Application Loader 3.0 (bundled with Xcode 6.2) or 3.1 (bundled with Xcode 6.4) solved the problem.

Titanium content assistant not working

The content assistant is not working.
I'm working on OSX, Titanium Studio, iOS & Android mobile app and have tried the following:
Installing the following SDKs: 3.2.0, 3.2.1, 3.3.0.
Tried reverting between those versions.
Checked the Project Natures (mobile - primary, mobile module, are checked).
Tried every option on the Project Build Path.
Of course tried to build the project again and again.
Check the content assistant preference both in the main preference and in the project properties.
Are the any more suggestions?
I believe this is a bug in the 3.2.0GA SDK (3.2.1 and 3.3.0 are not official releases yet). As far as I have heard it is known and should be fixed in the next SDK update. Only question is when this update will be out.
You can get content assist back by reverting to 3.1.3GA, but that doesn't help you much if you need features from 3.2.0GA.
EDIT:
The issue is described in this JIRA-ticket and as it mentions should be resolved in the upcoming 3.2.1 release.