Unable to install .ipa from apple configurator 2 and xcode - xcode

This is my first app to try to distribute, a beginner here. Please help me
I have created an app with Expo React Native and wanted to distribute it to my friends for testing. I generate the .ipa file with the command below.
expo build:ios
Expo request for my credentials and some other details when I run the command above and I leave everything to the expo to handle the documents.
With the generated .ipa file above, I use Apple Configurator 2 to install my app, simply “add”>“apps”>“Choose from my mac”>select .ipa. The app appears in iPhone but darker colour and show "Unable To install ‘app-name’. Please try again later. " when I click it. Tried to install with Xcode as well but fail too.
Then I found someone able to solve this issue by register his iPhone’s UDID to the account. Done it but doesn’t work.
I have also created Ad Hoc Provisioning Profile and run it with the command above. For some reason, errors appear and fail to build my app to generate an .ipa file with it.
What should I do? Feel free to ask for more information. Can somebody help me to publish a standalone app with expo react native? What are the requirements? I want to install it on my phone only, not for public or commercial use.
One extra information, I have also downloaded a random .ipa file from the random website for testing. The result is failing to install as well. Same error.

Related

How to handle MISSING_PLUGIN_EXEPTION in Flutter with Firebase Core Plugin on IOS

for several days I have tried to link my Flutter app with Firebase Database. But unfortunately, whenever I want to start debugging the compiler gives back a missing plugin exemption concerning the firebase_core package. I have already seen some entries referring to this issue here on stack overflow but none of them worked for me.
I have already followed the instruction steps by the installation guide on Firebase and included the Google Service File in my Xcode project.
I already did flutter clean, deleted the pods folder and the pod file.lock file in IOS, tried to include the Firebase SDK package by using the add package option in Xcode.
In the past, the connection between my Flutter project and the Firebase Database already worked but somehow it won't work now.
I think that my issue deals with the new step in the installation process for Firebase Connection when I am asked to make use of the Firebase SDK in Xcode.
In the following I'll add some more pictures for illustration. If someone had the same/a similar issue, it would be a huge help for me.
error Message
podfile
main_dart
Xcode runner workspace including google Service
AppDelegate in Xcode
pubspec yaml

Image component flickering when navigating between pages React Native + Expo

I'm currently working on an app that has a database that stores the link to the image sources (it's not locally stored) and then in the app, I use that link for the source.
I get a white flickering when navigating and so far, all the solutions I've found are either not compatible with expo (react-native-fast-image) or not compatible with image links (using defaultSource).
Has anyone solved image flickering on Expo with a image not stored locally?
Today, we are pleased to announce that with the arrival of Expo SDK 42, you can now create custom development clients in the cloud using EAS Build, or locally with the new Expo run commands.
You can try it out today:
Create a new project: expo init
Install the packages: expo install react-native-fast-image expo-dev-client
Build the native app:
In the cloud with eas build -p all --profile development (expo build does not support custom builds)
Or locally with expo run:ios and expo run:android (note: see https://expo.fyi/prebuild-cleanup for information on the generated files)
To be clear, react-native-fast-image will not have been added to the Expo Go app that you download from the App Store or Google Play Store.
We still consider this feature to be completed because users can now create a custom client app that includes this library, without needing to write any native code.
We hope you enjoy, and we have big plans to continue improving this workflow going forward!
(с) Brent Vatne https://expo.canny.io/feature-requests/p/react-native-fast-image

Upload Build Using XCode 9

As IOS release its new updates we have IOS-11 now and to support we have Xcode9.
Xcode-9 has changes its upload process of build to i-Tunes and its quite unfamiliar for us to Follow the process.
Recently i need to upload the build but the selection of certificate section is quite confusing.
I have choose my distribution certificates but i it will not allow me to proceed further
Sometimes its says : 'Profile is not manually managed.'
Sometimes its says : Profile is not Appstore certificates.
Please if anyone can guide me How to Upload build using Xcode-9
Thanks.
I think choosing Automatically manage signing, and trying to upload a build using Application Loader will solve you problem.

Xcode Server Bot integration fails to export archive with Assertion fail: exportArchive: ipatool failed with an exception

I have a build server setup with Xcode 7.2 and Server 5.0.15 so we can have CI. I'm able to create an Xcode Bot that creates an archive, but it's not able to finish the last step, which is exporting the ipa archive to the Server so it can be downloaded via ad hoc builds.
I'm able to create an archive from a local machine, but whenever I run a build bot using Distribution as the scheme, I get this error...
Bot Issue for TEST-BUILD-BOT-3 (build service warning)
Integration #8 of TEST-BUILD-BOT-3
Open in Xcode: xcbot://(null)/botID/fa5f2ef869edbde2181109e01843e862/integrationID/fa5f2ef869edbde2181109e01847dbb0
Assertion: exportArchive: ipatool failed with an exception: #<Errno::EEXIST: File exists - /var/folders/3x/8t3j9vnj48530fxd4g4djp14000087/T/ipatool20160318-45875-5xq2zz/MachOs/iphoneos/armv7/(dylibs)/libswiftContacts.dylib>
File: (null):(null)
Full logs for this integration are attached.
For one thing, I'm not sure where the full logs are attached (this error is shown in the Xcode build bot window).
Some information on my project:
The project consists of an app with three extensions (share photo, share safari and watch).
I'm using Cocoapods with some swift frameworks, so I'm using the use_frameworks! keyword in my podfile.
I've tried the following:
Made sure all targets (including pods) were using the Distribution certificate.
Tried w/ and w/o Bitcode enabled.
The worst part about trying to fix this issue is that the build bot takes 20-30 minutes each time I want to test some changes I made.
Any suggestions would be much appreciated!
I had the same error, in the watchapp and watchapp extension targets, i changed the setting, under Build Settings
Embedded Content Contains Swift Code No
And the error was gone
I found this technical post from apple that says any embedded content needs to be set to No to prevent multiple copies of the swift library being added. I interpreted that as a watch target would be embedded content, (not sure if thats what they meant)

AdHoc build not getting archived with Titanium SDK 3.2.0

I have implemented cross platform application using Titanium 3.2.0 but when i try archiving the build for iOS AdHoc distribution, it does not get compiled. It keeps giving error with developer name as mentioned below - Invalid "--distribution-name" value ""
I tried building from XCode, Titanium UI and over Terminal as well but same error everywhere. I have referred https://jira.appcelerator.org/browse/TISTUD-5642 and it says that issue is fixed but i still face this issue over every machine updated to 3.2.0 or even when 3.2.0 is installed fresh.
Please help and provide information.
Regards.
Sounds like your Application IDs don't match from your project to your Provisioning Profile.
In your Tiapp.xml file, you may have and application id like com.mycompname.THISappname, but you told the Apple Provisioning Profile that your app id was called com.mycompname.OTHERappname. So they don't match. Change your Tiapp.xml file to match the what the Apple Provisioning Profile expects or creating another profile matching your application id in Titanium Studio.
this worked for me: create a new production certificate AND create a new provisioning profile with the same bundle ID. (Yes, this will work if you are updating an app that is already live). Download the cert and prov. profile and run both (double click). Now repeat step 6 and archive. This should work.

Resources