We had a lot of trouble connecting the system to the backend last week.<\/p>\n\n\n\n
Last week, I realised the significance and necessity of dealing with setup to the programmers. The initial problem was with the SSL certificate, which prevented us from creating a purchase order to test whether the service worked or not. This was a backend issue that was resolved by Mr. Peter.<\/p>\n\n\n\n
After that, we discovered another IP address issue, which required me to update all of the IP addresses with my computer’s IP address. Also, we discovered that the ports we declared were not the same as the ones on the docker. After making the necessary changes, we are now able to connect the produced API to the system.<\/p>\n\n\n\n
I provide a header to the API that includes the URL and the access token, but it doesn’t function and returns an error. After doing some research to figure out what that error meant, I discovered that we needed to install the After testing all of the requests, the service is now completely functional, and the responses are exactly what I expected. Also, all of this is created by a type model, with the exception of the error, which I will resolve next week.<\/p>\n","protected":false},"excerpt":{"rendered":" We had a lot of trouble connecting the system to the backend last week. Last week, I realised the significance and necessity of dealing with setup to the programmers. The initial problem was with the SSL certificate, which prevented us from creating a purchase order to test whether the service worked or not. This was … <\/p>\nreact-native-url-polyfill<\/code> library and add its function to the header to make\u00a0\u00a0everything to work properly, and that was the clue. After installing it and adding it to my API service, I was able to request the API and receive a 200 status.<\/p>\n\n\n\n