Testing the Atlassian-connect-express app

Hi, we have already developed “Crystal Gantt Pro” and deployed atlassian connect app which is running successful around 6 years or so. We have to test some feature within our app by making local changes?

How should we test our app with local changes before moving it into beta or prod?

We followed the same as earlier like, running our app locally and porting it on ngrok. When we tried to install our app on new atlassian site, it throws the below error,

index.2d1cb3b5.js:1 Uncaught ApolloError: Unexpected error from UPM task: connect.install.error.remote.descriptor.validation
    at new e (index.2d1cb3b5.js:1:1685794)
    at index.2d1cb3b5.js:1:1759571
    at o (index.2d1cb3b5.js:1:1764492)
    at index.2d1cb3b5.js:1:1764407
    at new Promise (<anonymous>)
    at Object.then (index.2d1cb3b5.js:1:1764374)
    at Object.next (index.2d1cb3b5.js:1:1764502)
    at y (index.2d1cb3b5.js:1:1700268)
    at v (index.2d1cb3b5.js:1:1700790)
    at e.next (index.2d1cb3b5.js:1:1701291)
    at index.2d1cb3b5.js:1:1767152
    at Array.forEach (<anonymous>)
    at r (index.2d1cb3b5.js:1:1767121)
    at Object.next (index.2d1cb3b5.js:1:1765268)
    at y (index.2d1cb3b5.js:1:1700268)
    at v (index.2d1cb3b5.js:1:1700790)
    at e.next (index.2d1cb3b5.js:1:1701291)
    at Object.next (react-root.e83a8e7a.js:21663:1099312)
    at y (index.2d1cb3b5.js:1:1700268)
    at v (index.2d1cb3b5.js:1:1700790)
    at e.next (index.2d1cb3b5.js:1:1701291)
    at react-root.e83a8e7a.js:32:194657
e @ index.2d1cb3b5.js:1
(anonymous) @ index.2d1cb3b5.js:1
o @ index.2d1cb3b5.js:1
(anonymous) @ index.2d1cb3b5.js:1
then @ index.2d1cb3b5.js:1
(anonymous) @ index.2d1cb3b5.js:1
y @ index.2d1cb3b5.js:1
v @ index.2d1cb3b5.js:1
e.next @ index.2d1cb3b5.js:1
(anonymous) @ index.2d1cb3b5.js:1
r @ index.2d1cb3b5.js:1
next @ index.2d1cb3b5.js:1
y @ index.2d1cb3b5.js:1
v @ index.2d1cb3b5.js:1
e.next @ index.2d1cb3b5.js:1
next @ react-root.e83a8e7a.js:21663
y @ index.2d1cb3b5.js:1
v @ index.2d1cb3b5.js:1
e.next @ index.2d1cb3b5.js:1
(anonymous) @ react-root.e83a8e7a.js:32
Promise.then
(anonymous) @ react-root.e83a8e7a.js:32
t @ index.2d1cb3b5.js:1
e.subscribe @ index.2d1cb3b5.js:1
(anonymous) @ react-root.e83a8e7a.js:21663
t @ index.2d1cb3b5.js:1
e.subscribe @ index.2d1cb3b5.js:1
complete @ index.2d1cb3b5.js:1
e.start @ index.2d1cb3b5.js:1
e @ index.2d1cb3b5.js:1
t.getObservableFromLink @ index.2d1cb3b5.js:1
t.getResultsFromLink @ index.2d1cb3b5.js:1
y @ index.2d1cb3b5.js:1
t.fetchQueryByPolicy @ index.2d1cb3b5.js:1
v @ index.2d1cb3b5.js:1
t.fetchConcastWithInfo @ index.2d1cb3b5.js:1
e.fetch @ index.2d1cb3b5.js:1
e.reobserveAsConcast @ index.2d1cb3b5.js:1
e.reobserve @ index.2d1cb3b5.js:1
r @ index.2d1cb3b5.js:1
i @ index.2d1cb3b5.js:151
setTimeout
(anonymous) @ index.2d1cb3b5.js:157
o @ index.2d1cb3b5.js:1
r @ index.2d1cb3b5.js:1
i @ index.2d1cb3b5.js:151
setTimeout
(anonymous) @ index.2d1cb3b5.js:157
o @ index.2d1cb3b5.js:1
e.updatePolling @ index.2d1cb3b5.js:1
e.startPolling @ index.2d1cb3b5.js:1
y @ user-connected-apps.826b4664.js:31
(anonymous) @ user-connected-apps.826b4664.js:24
lv @ index.2d1cb3b5.js:84
ck @ index.2d1cb3b5.js:84
cs @ index.2d1cb3b5.js:84
aE @ index.2d1cb3b5.js:84
cr @ index.2d1cb3b5.js:84
ig @ index.2d1cb3b5.js:84
p.subscribe.dirty @ react-root.e83a8e7a.js:21852
(anonymous) @ index.2d1cb3b5.js:124
w @ index.2d1cb3b5.js:124
(anonymous) @ index.2d1cb3b5.js:124
O @ index.2d1cb3b5.js:124
t @ index.2d1cb3b5.js:124
o @ index.2d1cb3b5.js:124
Promise.then
submit @ index.2d1cb3b5.js:124
n.submit @ index.2d1cb3b5.js:124
h @ react-root.e83a8e7a.js:21852
t$ @ index.2d1cb3b5.js:84
t1 @ index.2d1cb3b5.js:84
(anonymous) @ index.2d1cb3b5.js:84
rI @ index.2d1cb3b5.js:84
rx @ index.2d1cb3b5.js:84
(anonymous) @ index.2d1cb3b5.js:84
cu @ index.2d1cb3b5.js:84
tW @ index.2d1cb3b5.js:84
rL @ index.2d1cb3b5.js:84
ne @ index.2d1cb3b5.js:84
e7 @ index.2d1cb3b5.js:84
i @ index.2d1cb3b5.js:151

#1 - How to test my local changes on previously installed site?

#2 - Why is this issue comes when i try to install as an new app? How to pass through it?

Hello @rajagopal

This could be caused by several things. Possible causes may include:
Schema validation issues in the descriptor JSON
Atlassian not being able to reach your descriptor (e.g. ngrok tunnel issue, HTTPS problem)
Or even potential Marketplace conflicts (e.g. using the same app key locally as one already published) - not really sure here though.

Also worth noting: the Atlassian Connect platform is being gradually deprecated. You can read more about the official timeline and migration plans here:
:backhand_index_pointing_right: Atlassian Blog – Connect End of Support Timeline and Next Steps