Request could not be processed

47 views
Skip to first unread message

Christian Jansen

unread,
Oct 11, 2022, 7:04:00 AM10/11/22
to basespace-developers
Dear Basespace developer Community,

I am currently developing a prototype native basespace app for my employer.
So far I was able to add a docker image to a private repository, which I have tested locally with no issues arising.
Also I already have an input form ready from which I am now trying to simulate a launch in order to get the the AppSession.json file to further develop my docker image. I was able to do this in the past, however since a few days whenever I try this it gives the following error.

Unexpected Issue
Your request could not be processed.

Use your browser Back button to try again. If the problem persists, contact Technical Support or return to the Dashboard


I already contacted the support like described in the message and they forwarded me here.
Does anyone of you have experience with this issue and can give me advice or directions?
If you need further information for debugging please don't hesitate to ask.

Thank you very much in advance for your help!
Best regards,
Christian

Nick Vinckier

unread,
Oct 11, 2022, 10:02:50 AM10/11/22
to basespace-developers
Are you able to share your form builder json and dickey image here? As a test, have you tried flipping the docker repo to public briefly, to rule out any permissions issues when pulling from within the app?


--
You received this message because you are subscribed to the Google Groups "basespace-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to basespace-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/basespace-developers/53ff2480-4571-4060-b29a-48a187a5475an%40googlegroups.com.

Christian Jansen

unread,
Oct 13, 2022, 3:50:19 AM10/13/22
to basespace-developers
Hi and thanks for the quick reply!
I attached my inputform below. The dockercontainer I can't share as easily, because it contains some company internal pipelines which I can't publish without permission.
I also can't imaginge that the docker container has something to do with it since it should not have an influence on a simulated launch in my understanding. I will however test this with replacing it with the demo docker container and seeing wether it works.

Best regards Christian
inputform.json

Christian Jansen

unread,
Oct 14, 2022, 5:41:52 AM10/14/22
to basespace-developers
I have just tested to simulate a launch with the example docker container in the callback.js script and the same error emerges. Therefore the error seems to either be located in the inputform or in basespace itself.

Has anyone experienced something similiar so far or seen this error?

Christian Jansen

unread,
Oct 17, 2022, 6:00:59 AM10/17/22
to basespace-developers
Quick update form my side,
I narrowed down the problem even further by retracing my development steps.
The problem started after switching from a simple SampleChoose to a TabularFieldSet with multilple inputs.
When changing back to the SampleChooser I was able to successfully simulate a launch again.

Additionally I then tried to replace the SampleChooser with the example TabularFieldSet from the documentation, however this did not work either.

Did anyone of you use this kind of table in their projects and would be able to give advice on where I might have gone wrong?

Thank you again for your help and best regards,
Christian Jansen

Here ist the json part of my input TabularFiledSet:

{
"$type": "TabularFieldSet",
"id": "sample-experiments",
"seriesHeader": "",
"maxrows": 2,
"headers": [ "Samples" ],
"fields":
    [
        {
        "$type": "SampleChooser",
        "size": 300,
        "allowedPermissions": "read",
        "required": true,
        "requiredMessage": "Please choose a sample",
        "multiselect": true,
        "id": "control-samples",
        "rules": "",
        "displayFields": [
            {               
                "$type": "Select",
                "id": "select-sex",
                "label": "Biological sex",
                "multiselect": false,
                "choices":[
                     {
                        "value": "f",
                        "text": "Female",
                        "selected": true
                     },
                     {
                        "value": "m",
                        "text": "Male",
                        "selected": false
                     }
                ]
             }
            ]
        }
    ]
},

Christian Jansen

unread,
Oct 19, 2022, 4:31:44 AM10/19/22
to basespace-developers
Hi everyone,
For future reference I managed to fix the issue on my own.
It seems to have been linked to either the missing rules in the sample choose and/or the fact that part of the TabularFieldSets were multiselect while others were not.
In the attachments you find my fixed version of the inputform.json

Best regards,
Christian
inputform.json
Reply all
Reply to author
Forward
0 new messages