Unable to create new posts.

[MohitMaulekhi]

Describe the bug
Getting server not running/ invalid url error message while creating new posts.

To Reproduce
Steps to reproduce the behavior:

1. Login/register with an account.
2. Create posts.

Expected behavior
New posts should be created.

Actual behavior
Getting error message server not running/ invalid url

Screenshots

[MohitMaulekhi]

Assign

[github-actions]

Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.

[noman2002]

@MohitMaulekhi Are you running the talawa-api locally ??

[MohitMaulekhi]

@MohitMaulekhi Are you running the talawa-api locally ??

Yes, I am running the talawa-api locally. I’ve verified that the server is up and running without any errors. The configuration files and API endpoint URL have also been double-checked to ensure they are correctly set. However, I’m still encountering the "server not running/invalid URL" error message while creating new posts.

Mr. Parag mentioned that a GSoC project from this year changed the schema of the post. So, it seems we need to fix this before we can start posting.

Could you also remove the "invalid" tag from this issue?

[Sangharshdeveloper]

Assign

[MohitMaulekhi]

@palisadoes @noman2002

Are we using the imageUrl and videoUrl fields in the Post model?

These fields are not being sent by the GraphQL backend query, but the Post model and frontend expect them. I haven't seen any usage of these fields in the app.

Are we using the File field for attachments?

This field is being sent by the GraphQL backend query.

Removing the imageUrl and videoUrl fields from the app fixes the unwanted server not running/invalid URL error message, but changes should be made in the frontend post queries and models regarding the File field.

Please advise on how to proceed.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

Unassigned. Inactivity