Flask test_client always returns 404 in connexion 3.0.3 about connexion HOT 10 CLOSED

Happenning the same here but using Swagger UI, so the problem may not be specific to test_client but to general API routing.

What's more, maybe issue #1823 may help by fixing starlette version

from connexion.

This is because Connexion lazily initializes the routing when the first ASGI call is received.

Workaround:

            # Workaround for race condition in connexion initialization
            # pylint: disable=protected-access
            connexion_app.middleware.app, connexion_app.middleware.middleware_stack = \
                connexion_app.middleware._build_middleware_stack()

Excuse the comment, (it also causes a race condition in startup if you're using werkzeug with threads, and a wsgi-asgi converter).

Correct solution is probably to convert your unit tests to use the provided startlette TestClient, but that involves some work as the API is significantly different. connexion_app.test_client()

from connexion.

The issue is being discussed on the starlette repo here.

from connexion.

3.0.4 has been released containing this fix.

from connexion.

Are you still using the Flask test client? Because that is not expected to work anymore. You should use the Connexion test client.

from connexion.

Happenning the same here but using Swagger UI, so the problem may not be specific to test_client but to general API routing.

What's more, maybe issue #1823 may help by fixing starlette version

Thanks for your reply!
I tried multiple versions of starlette 0.27, 0.32.0.post1 and 0.33 but it did not help.

from connexion.

Thanks for the reports everyone. I just submitted #1828 to set an upperbound to our Starlette dependency. We'll release it as soon as possible and will investigate the underlying issue afterwards.

from connexion.

Closing in favor of #1824

from connexion.

@RobbeSneyders Thanks for the quick update!
Unfortunately it also does not work with connexion 3.0.4 and starlette < 0.33.
In #1824 there is a different error which seems to be fixed with the pinned starlette version.

Same error as in the first post:
werkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.

from connexion.

Are you still using the Flask test client? Because that is not expected to work anymore. You should use the Connexion test client.

Yes I tried the Flask test client. Alright thanks, I just switched to the connexion test client and got it working with POST/PUT request. For anyone interested:

Before (Flask test client):

response = app.put(
    "/myroute",
    content_type="application/json",
    data=json.dumps(body),
    query_string={"param": param},
)

After (Connexion test client):

response = app.put(
    "/myroute",
    headers={"Content-Type": "application/json"},
    data=json.dumps(body),
    params={"param": param},
)

There are also some changes needed with checking the response, but I will figure it out :)

from connexion.