Project Config Cache is not updating Xcode version
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Accessibilité débutants
- 35/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- À l'abandon
- Stack technique
- ios, javascript
- Domaine
- cli, mobile-dev
Piste de recherche
Commencez par reproduire l’écart avec ns run ios --log trace et ns doctor, en vous concentrant sur les informations mises en cache du Project Config Service et sur la version de Xcode signalée. Suivez la manière dont le cache est lu pendant ns run ios et comparez-le à la valeur actuelle fournie par ns doctor ; le travail est terminé lorsque les deux commandes indiquent la version actuelle de Xcode.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):
- CLI: 7.0.8
Describe the bug
When running ns run ios --log trace the Project info that is displayed doesn't reflect the same info from ns doctor.
This is the relevant piece from ns run ios --log trace. If you compare the Xcode version shown here it doesn't match the Xcode version when I run ns doctor.
Project Config Service using legacy configuration...
Initializing analytics statuses.
Analytics statuses: { TrackFeatureUsage: 'disabled', TrackExceptions: 'disabled' }
getInfos cacheConfig options: { forceCheck: undefined } current info from cache: [ { message: 'Xcode is installed and is configured properly.',
platforms: [ 'iOS' ],
type: 'info' },
{ message: 'xcodeproj is installed and is configured properly.',
platforms: [ 'iOS' ],
type: 'info' },
{ message: 'CocoaPods are installed.',
platforms: [ 'iOS' ],
type: 'info' },
{ message: 'CocoaPods update is not required.',
platforms: [ 'iOS' ],
type: 'info' },
{ message: 'CocoaPods are configured properly.',
platforms: [ 'iOS' ],
type: 'info' },
{ message: 'Your current CocoaPods version is newer than 1.0.0.',
platforms: [ 'iOS' ],
type: 'info' },
{ message: 'Python installed and configured correctly.',
platforms: [ 'iOS' ],
type: 'info' },
{ message: 'The Python \'six\' package is found.',
platforms: [ 'iOS' ],
type: 'info' },
**{ message:
'Xcode version 11.5.0 satisfies minimum required version 10.',
platforms: [ 'iOS' ],
type: 'info' }** ]
Xcode is installed and is configured properly.
xcodeproj is installed and is configured properly.
CocoaPods are installed.
CocoaPods update is not required.
CocoaPods are configured properly.
Your current CocoaPods version is newer than 1.0.0.
Python installed and configured correctly.
The Python 'six' package is found.
**Xcode version 11.5.0 satisfies minimum required version 10.**
Result from ns doctor
No issues were detected.
✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ The Android SDK is installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Xcode is installed and is configured properly.
✔ xcodeproj is installed and is configured properly.
✔ CocoaPods are installed.
✔ CocoaPods update is not required.
✔ CocoaPods are configured properly.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
**✔ Xcode version 12.0.0 satisfies minimum required version 10.**
I'm not sure how to clear the cache that's being picked up on ns run ios but I'm having issues with the command line starting the app on my phone with iOS 14. I can start it fine from Xcode but it won't start from ns run ios and I think it might be related to ns run ios using an old Xcode version.
- Langage dominant
- JavaScript
- Étoiles
- 1.1k
- Forks
- 204
- Merge moyen
- 1 j 9 h
- PR mergées (30 j)
- 8
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de NativeScript/nativescript-cli
-
in-progress
NativeScript/nativescript-cli#6140 · 2 commentaires · 1 personne assignée ·
-
NativeScript/nativescript-cli#6090 · 1 personne assignée ·
-
in progress
NativeScript/nativescript-cli#6015 · 1 réaction · 1 personne assignée ·
-
question
Difficulté 4/5 3-5 jours Accessibilité débutants 48/100
NativeScript/nativescript-cli#5992 · 5 commentaires ·
-
feature-pending-triage
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
NativeScript/nativescript-cli#5975 ·
Toutes les issues de NativeScript/nativescript-cli
Issues similaires
-
enhancement
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
babalae/bettergi-scripts-list#3674 ·
-
ecosystem wording
Difficulté 1/5 Moins d'une heure Accessibilité débutants 90/100
matrix-org/matrix.org#3649 ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 88/100
vadimdemedes/ink#1029 ·
-
code-quality refactoring
Difficulté 2/5 1-3 heures Accessibilité débutants 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
langchain-ai/deepagents#6450 ·