Error in the certification process due to the lack of types in the libraries

Victor0814gui commented 1 year ago

Problem Description

This is the second application I try to publish, but the types are not found by the APP Certification Kit. What is the way to work around this?

Steps To Reproduce

1.Create an application with third-party libraries and submit it to the Microsoft Store.

Expected Results

Successfully published in the store.

CLI version

11.3.6

Environment

info Fetching system and libraries information...
System:
  OS: Windows 10 10.0.19045
  CPU: (4) x64 Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz
  Memory: 1.23 GB / 7.93 GB
Binaries:
  Node:
    version: 18.17.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn:
    version: 1.22.19
    path: C:\Program Files\nodejs\yarn.CMD
  npm:
    version: 9.6.7
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK:
    API Levels:
      - "28"
      - "29"
      - "30"
      - "31"
      - "32"
      - "33"
    Build Tools:
      - 29.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
    System Images:
      - android-26 | Google Play Intel x86 Atom
      - android-28 | Wear OS Intel x86 Atom
      - android-28 | Google APIs Intel x86 Atom_64
      - android-31 | Intel x86 Atom_64
      - android-31 | Google TV Intel x86 Atom
      - android-31 | Google APIs Intel x86 Atom_64
      - android-31 | Google Play Intel x86 Atom_64
    Android NDK: Not Found
  Windows SDK:
    AllowDevelopmentWithoutDevLicense: Enabled
    AllowAllTrustedApps: Enabled
    Versions:
      - 10.0.18362.0
      - 10.0.19041.0
      - 10.0.22000.0
      - 10.0.22621.0
IDEs:
  Android Studio: AI-221.6008.13.2211.9619390
  Visual Studio:
    - 17.7.34009.444 (Visual Studio Community 2022)
Languages:
  Java:
    version: 11.0.15
    path: C:\Program Files\OpenJDK\openjdk-11.0.15_10\bin\javac.EXE
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.1.0
    wanted: 18.1.0
  react-native:
    installed: 0.72.4
    wanted: ^0.72.3
  react-native-windows:
    installed: 0.72.8
    wanted: 0.72.8
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: false
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Target Platform Version

10.0.19041

Target Device(s)

Desktop

Visual Studio Version

Visual Studio 2022

Build Configuration

ReleaseBundle

Snack, code example, screenshot, or link to a repository

No response

### Tasks

jonthysell commented 1 year ago

@chiaramooney , are we hitting this with Gallery? Would Gallery pass this certification?

@Victor0814gui Have you tried uploading the appx to see if the Store actually complains about it?

Victor0814gui commented 1 year ago

Yes @jonthysell, I tried uploading through Visual Studio and also sending the .appxupload file directly, but I was not successful.

Victor0814gui commented 1 year ago

I created a sample repository based on an existing product for testing purposes. I hope I won't be sued by Microsoft, haha, since the Microsoft Store is quite strict with new applications.

https://github.com/Victor0814gui/settings-11-clone

chiaramooney commented 11 months ago

Currently we have apps in the store running on RNW v0.72 (see React Native Gallery). We also have an app in the store running on v0.73.0-preview.0. Both of these published with no WACK issues. My guess would be this error is coming from a community module that your app is using.

chrisglein commented 11 months ago

Error as text (thanks OCR!):

The Microsoft.ReactNative. IJSValueReader type referenced by the RNScreens. IRNScreensModule type in the file C:\Program Files\WindowsApps\35657ivgc.builder.Settingswin11clonestudy_1.0.2.0_x64_yg0tzxzkv29bc\RNScreens.winmd was not found. All types referenced in metadata files must be discoverable.

I assume the problem here is something to do with this version of RNScreens (we have our Gallery app publishing to the store, but on an older version), or in the project configuration.

From your project configuration, UseExperimentalNuget is turned on.

This may be an issue with how the nuget package dependencies are set up, particularly with react-native-screens (and it having an older version of the module template).

Actions we should take:

Put Gallery on the latest version of Screens
Check the Screens module's configuration to see if it's doing the right things with nugets.

Unblocking actions on your end:

Try turning off UseExperimentalNuget in your this file: https://github.com/Victor0814gui/settings-11-clone/blob/main/windows/ExperimentalFeatures.props

Victor0814gui commented 10 months ago

It makes sense, I will migrate and see if this solves the issue. Thank you very much for the response.

microsoft / react-native-windows