45
Views
11
Comments
Solved
[Multiple Selection Dropdown (ReactAndMob)] Incompatible widget and broken references error when deploying to non-production env
Application Type
Reactive
Service Studio Version
11.53.18 (Build 61343)

Hi All,


Context:
I'm getting an incompatible error and broken references error with "Multiple selection dropdown widget" when deploying my application from dev to uat in lifetime even when while installing that particular widget it gave me no error/warning what-so-ever.

No issues while installing the widget:

Issues when deploying application to uat:

1. broken references error

2. incompatible error with the widget


I have no idea why the widget gets installed perfectly without any issues/warnings/errors, but gives problems during deployment.


Thanks & Regards,

Aman Devrath

UserImage.jpg
Chris Stacey
Solution

Hi Aman,

I'm glad we were able to finally get things working for you!  (via private messages) 

For the benefit of readers at a later date...
The issue was that the MultiSelect_ReactAndMob widget app needed to be deployed to the new environment, with the app that depends on it. The error occurred when the "Do Nothing" option was used.

As I'm sure every developer will appreciate, the simple things get even the best of us from time to time.

All the best with your developing Aman! :)

Sincerely,
Chris.

2024-04-15 16-08-47
Aman Devrath
Solution

Adding to the answer provided by Chris :

I selected "Deploy 0.1.1" option (or any other version that you see above the 'Do Nothing' option) for the component. Deployed the component first to environment. Then I selected the app, validated to check for any other errors, and then deployed the application. 

Or you deploy both together as the image below.


Thank you for the help Chris.

UserImage.jpg
Chris Stacey

Hi Aman,

This is a new issue to me, although I have had many frustrating hours of reference problems in OutSystems :(

I will try to help as best I can.

Have you tried re-opening each module, refreshing the references, re-publishing them one-by-one,  and then deploying again?

Are there any further clues in the 'show details' hyperlinks?

Chris.

2024-04-15 16-08-47
Aman Devrath

Hi Chris, 

I've re-opened each module, though there are only 2-3 modules that I'm using in my current application. 

I've even removed unused dependencies as I was getting an error with another widget which wasn't being used. From Multi selection dropdown widget, only the license block was removed as i'm not using it in my application ( if this is not okay, i can add it again).

"Show details" shows a popup:


Thanks,

Aman

UserImage.jpg
Chris Stacey

Hi Aman,

Hmmm...

Flying in the dark. Here are my suggestions in order...

  1. Are you able to install the MultiSelect_ReactAndMob DEMO into development environment #3 without error?
  2. Are the environments the same Version number?
    (development environment #3 and non-production environment #..)
  3. What happens if you try deploying the multi-select app on its own first?
  4. Are you able to download/install the MultiSelect_ReactAndMob APP to the non-production environment #..  from the forge?
  5. Are you able to install the MultiSelect_ReactAndMob DEMO into non-production environment #.. without error?

Sincerely,
Chris.


2024-04-15 16-08-47
Aman Devrath

Hi Chris,

1. I downloaded the .oap file from the forge. On opening it with service studio, I got this message.

I couldn't open it in browser, got below error:

2. Both environments are same version

3, 4 & 5 - I can't do this. I'm not authorized to install/deploy on my own in non-production environment. 


Thanks,
Aman.

UserImage.jpg
Chris Stacey

Thanks Aman!

Are you able (with authorisation) to try deploying just the MultiSelect_ReactAndMob app to non-prod?

Regarding 1, I'm waiting for OutSystems to respond to support ticket(s).
(see https://www.outsystems.com/forums/discussion/82264/i-can-not-install-demo-multiple-selection-dropdown-widget/)

I only point it out in case it turns out the two problems are caused by the same underlying factor. You are the first to report an issue of this sort.

2024-04-15 16-08-47
Aman Devrath

Hi Chris, 

I'll try to ask someone from authorized devs to deploy the MultiSelect_ReactAndMob app to non-prod.

Let's hope that OutSystems responds back soon on your support ticket. 
Meanwhile, thanks for raising the ticket and for other suggestions.


Regards,

Aman

UserImage.jpg
Chris Stacey

Thanks!
I hope OutSystems responds quickly too.
You are most welcome!

UserImage.jpg
Chris Stacey

Hi Aman,

I sent you a message via OutSystems, I'd like to help you solve this if I can.
How did you go so far?

Chris.


PS: It's unlikely these are related, but just in case, the other issue got solved.

2024-04-15 16-08-47
Aman Devrath

Hi Chris,

I was on vacation until today, hence didn't get any chance to move ahead with it. 

Unfortunately, things are still same.

1. When I removed MultiSelect_ReactAndMob component and Demo, I didn't have any errors during deployment.

2. When I Installed MultiSelect_ReactAndMob component

     2.1. no issues while installing component

     2.2. Error during deployment when selected "Do Nothing"

     2.3. No error when selected "Deploy 0.1.1" in MultiSelect_ReactAndMob

I'll try asking my colleague when he comes back monday to deploy 0.1.1 of MultiSelect_ReactAndMob first and then check if there are any errors with my app.

PS: Didn't get any errors while installing Demo and no popup messages what-so-ever.

I don't know what is this incomptability/broken references error while I deploy my app. 


Thanks & Regards,

Aman Devrath

UserImage.jpg
Chris Stacey
Solution

Hi Aman,

I'm glad we were able to finally get things working for you!  (via private messages) 

For the benefit of readers at a later date...
The issue was that the MultiSelect_ReactAndMob widget app needed to be deployed to the new environment, with the app that depends on it. The error occurred when the "Do Nothing" option was used.

As I'm sure every developer will appreciate, the simple things get even the best of us from time to time.

All the best with your developing Aman! :)

Sincerely,
Chris.

2024-04-15 16-08-47
Aman Devrath
Solution

Adding to the answer provided by Chris :

I selected "Deploy 0.1.1" option (or any other version that you see above the 'Do Nothing' option) for the component. Deployed the component first to environment. Then I selected the app, validated to check for any other errors, and then deployed the application. 

Or you deploy both together as the image below.


Thank you for the help Chris.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.