developing using UE5 and EOS
testing using EOS Plus at the moment, I have logging in working fine now with steam and EOS (just as a test), my steam account is linked to my epic games account, however when I call the ReadFriendsList api with the code below (and many variations of this code to make sure it wasnt just me)
I get this error message
LogTemp: Warning: bWasSuccessful: 0
[2022.05.09-07.27.24:370][800]LogTemp: Warning: ErrorStr: EOS_Connect_QueryExternalAccountMappings() failed with result code (EOS_InvalidParameters)
I have all the below settings turned on
anyone got any ideas?
I reported the bug with Epic Games EOS Team directly, looks like this is a bug that may have been introduced 6 months ago, it is with the devs and should be fixed soon
for reference this was not working as of the UE5.0.1 and UE5.0.2 updates so anyone in future can get a time reference
Related
So my problem is pretty niche so I'm not sure it will have an answer from the community, but I guess it's worth a try cause I'm hitting a wall. I am trying to call an 8x8 api and getting results, but for some reason. I'm only getting a portion of what should be there. I have these variables X-Page: 9
X-Total-Pages: 38
X-Total-Elements: 37463
and my url is like this
"https://api.8x8.com/analytics/cc/v5/historical-metrics/3511365/data?page=9&size=1000" but when I switch it to page=10 I immediately get this error
"Bad request: Field 'page' must be greater than or equal to 0 and less than the total number of pages, which is 0 for this request"
It doesn't seem to make sense because based on the variables I should have 38 total pages to work with. I've been trying to search but I haven't seen anyone else have a similar issue.
It seems like the issue I'm having is relative to the report I'm trying to pull. Cause the other reports I ran worked. So I don't think it's a problem with my code or postman at all, seems like 8x8 issue. I opened a ticket to investigate.
Recently all my Shopify apps have stopped working due to this error. I can still pull data from the api (photos, titles, etc) but I can no longer add items to my cart or check out. this error isn't just happening on my current build but previous builds too. I think I might have made too many requests due to refreshing pages and have been banned from the API temporarily (I've had this happen with another API before). but it's now been 2 days and still no fix.
I'm pretty confident there's nothing wrong with my code because it's happening to other websites that were working before & haven't been touched for a while.
package used: "shopify-buy": "^2.11.0"
Thanks,
Mitchell D
turns out this error occurred because I was in PAUSE AND BUILD mode. so I must be on a plan to add items to the cart using the API? they must have made this change recently
Ok this sounds pretty dumb.
We use apache/tomcat # my company for our products.
I was fixing an internal server error and pressed refresh on chrome. It worked but now trying to make an internal article for my team and forgot what the second part of the error message said.
Is there anyway to see that previous page on Chrome.
Frustrating issue with attempting to use REST to login to the BIM 360 Field API, it was suggested that to use the postman application in order to ensure that my code wasn't an issue, however I'm now getting an unauthorized error, this has been attempted with an admin account and a developer account with the same response (login details are definitely valid), I was wandering if anyone has encountered this problem before or has any idea how would go about getting past this, I need to get the ticket response in order to go any further with developing an application for this, I'm already in contact with someone from Autodesk but due to timezone differences responses are difficult!
I've attached a picture to highlight the simplicity of what I'm attempting to do with no joy!
Thanks in advance
Dan
In case somebody else hits the same issue, FYI -
Dan and I looked at this issue, and we learned (in a hard way) that the base URL for BIM 360 Field in European region is:
https://bim360field.eu.autodesk.com
Notice "eu" in the URL. In the U.S., it is https://bim360field.autodesk.com
I wrote a post about this, too, for future reference:
https://fieldofviewblog.wordpress.com/2016/08/18/base-url-for-bim-360-field-in-european-countries/
I also found it worked when I used https but not http although the examples in the help use http.
I am getting this error when trying to add weight ranges to shipping carriers that I have. It mostly seems to happen at random and I have been able to complete some of the carriers but others will cause the error every time. The console reports the following: Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Is there a solution for this? I couldn't find anything online about it.
I have v. 1.6.1.4
Thank you!
You have to use firefox developper and when you get the "Parseerror"
using the developper tools you go to network and select your last query.
On the right you have a window with all the options of the query : cookies parameters... select response.
You should see the response of the parse error.
For me it was just a parameter of the form that could not be empty.
Putting a random word made everything work fine.
The same thing happened to me when adding weight ranges.
The annoying thing is i had to restore a backup of the tables ps_range_weight and ps_carrier.. as for every single instance of
"Prestashop Technical Error: Details: Error Thrown: [Object Object] Text Status: Parsererror" it made a new entry and i ended up with over 700 weight ranges.
Anyways, i restored to the last fucntioning versions of ps_range_weight and ps_carrier (needed doing) and disabled the standard paypal plugin from prestashop. After that it worked fine.
.
Hope this helps someone.
I have found a solution for this on Prestashop 1.7
This happened to me as well when I changed the theme, however, I checked the Database and found that the carrier ID in ps_range_weight has randomly changed!
Solution
Fix the carrier ID in the database to the correct one and this error should not be appearing again! Good luck
ps_range_weight