Upload SPFx built on 1.5 with beta packages to catalog fails on some tenants

[shaipetel]

Category

• Question
• Typo
• Bug
• Additional article idea

Expected or Desired Behavior

Drag spfx package file sppkg into sharepoint online app catalog should show the dialog to trust it, and install it.

Observed Behavior

On some tenants this installs correctly. However on a few of our test tenants and some of our customers, this package is uploaded without showing the dialog. It will add a package where all meta data fields are empty, version shows 1.0.0.0 which is wrong, and the "app package error message" will simply say "Error in the application" without giving any more information.

The same package will install on other tenants.

On the problematic tenants, installing a previous build that was using SPFx 1.4 works and installs correctly.

Steps to Reproduce

Build a package using SPFx 1.5 (I am not sure if this happens with every SPFx 1.5 package) and that uses the beta packages.

Try to add it to app catalog.

Is there a problem with installing an SPFx using beta packages? Is this not supported? I'd like to give some customers a preview of new features to try out.

Thanks.

FYI @VesaJuvonen, your input is always greatly appreciated!

[shaipetel]

I'd like to add:

The older version 1.0.0.7 installs correctly, but does not show any web parts on the site where I added it.

None of the web parts in this package are available.

This package was released a while ago and we have hundreds of installs already with no problems for months...

[shaipetel]

Here is how it looks like (the error message):

[shaipetel]

FYI the "Unavailable apps" view doesn't give much more info:

Not sure if related, but deleting this and installing the 1.0.0.7 version (older) works, but when adding it to sites it just took me 1.5 hours to finish adding the app to 1 site.

[shaipetel]

Could this be the issue?
pnp/sp-starter-kit#6

It says he had similar problems and it worked once he put his tenant in "Targeted release for everyone"?

It does work for me on the tenant that has this setting.
It doesn't work on a tenant that is set to standard release.

If that is the cause - can you please confirm, and explain why since SPFx 1.5 is in GA and not in beta. Why would it require targeted release to be turned on?

(I can't confirm this is the solution since we don't want to set that specific tenant to targeted release. We use it to test apps in standard release environment)

[msft-github-bot]

This issue is being closed as part of an issue list cleanup project. Issues with no activity in the past 6 months that aren't tracked by engineering as bugs were closed as part of this inititive. If this is still an issue, please follow the steps outlined to re-open the issue.