The server not responding please try again.

AChrist

• Your mobile device and operating system (e.g.: iPhone 5 - iOS 6.1, Samsung Galaxy SIII - Android 4.2.1, etc)
• Your country
• Type of bug (i.e.: technical issue, typo, UI, user experience, etc)
• Detailed explanation of the bug
• Steps to reproduce (if relevant)
• Screenshot (you can attach this as a file, only if relevant)

 

1) Google Nexus 7 16gb (Android 4.2)

2) Moldova (but I tried it to launch when I was in Ukraine - same error)

3) Failed to pass loading screen.

4) When I launch application - I get error everytime "The server not responding please try again." No matter how many times I do retry.

5) See #4.

6) attached

Romi

Thanks for the report - we're looking into it.

Debster

Hey, I am running into the SAME issue, but from my laptop. I did log a ticket, but I don't want to wait 4 days to get my money. Has this issue been resolved? I was told that it was not Payoneer issue, but it has to be. I even tried from my cell phone and got the same error. I can get to the Community page and Support pages, but not any pages related to my account. 

 

Is anyone else having this problem???

Romi

Hi Debster,

 

If you're referring the mobile app not showing My Account properly, we'll look into it and fix it. 

On your laptop you need to use: https://myaccount.payoneer.com/Login/Login.aspx to log in.

 

Please try again and let me know if you get an error.

kloni

identical problem as for AChrist
the device is Acer a100 tablet, Android version 4.0.3, country Croatia

justzamir

Getting this message on my Laptop

 

Service Unavailable - Zero size object

The server is temporarily unable to service your request. Please try again later.

Reference #15.51aa3451.1381050568.4a0d0f2

Romi

justzamir wrote on October 6 2013, 9:11 AM: »

Getting this message on my Laptop

 

Service Unavailable - Zero size object

The server is temporarily unable to service your request. Please try again later.

Reference #15.51aa3451.1381050568.4a0d0f2

 

We're experiencing some technical issues right now and are working on solving this ASAP. Thank you for your patience.

 

Update: The technical issue has been resolved. A power outage resulted in our website being down for a short time, and this issue has been resolved. Sorry for the inconvenience!

Howard Rubin

Android 4.3
Asus Nexus 7 (ME370T)
Kernel 3.1.10-e8b3d8
Build JWR66Y
Default browser Chrome 30.0.1599.82
Device language - English
Country - Brazil
App language - English
1,280 x 800 Pixels
Screen Position (Portrait or Landscape)- Testing Both
Wifi only
Device Carrier N/A
Frequency - 4 of 4

 

Technical issue - Server error, the server is not responding please try again.

 

Happens just starting app, three weeksI have tried running it different times of the day.  remove data, uninstall, re-install several times.

 

Are you connecting to Brazil?

 

 

elvanja

Romi wrote on October 6 2013, 10:40 AM: »

We're experiencing some technical issues right now and are working on solving this ASAP. Thank you for your patience.

 

Update: The technical issue has been resolved. A power outage resulted in our website being down for a short time, and this issue has been resolved. Sorry for the inconvenience!

 

I'm still having this issue.

Using Nexus 7 32G, latest Android updates.

I've installed the application over Google Play Store.

 

When I start the application, the initial screen shows, empty, and after a while I get the "The server not responding please try again" message and that's it.

Tried after several restarts of the device, every time the same scenario occurs.

 

I am in Croatia, if that can help.

Thanks!

Nissim

Hi Guys,

 

We believe the issue is being caused by sim-free devices (devices not connected to a mobile network).

 

Our dev team is looking into the issue and we hope to have it resolved in the next version update, or by version 2.0.

elvanja

Nissim wrote on October 11 2013, 11:52 AM: »

Hi Guys,

 

We believe the issue is being caused by sim-free devices (devices not connected to a mobile network).

 

Our dev team is looking into the issue and we hope to have it resolved in the next version update, or by version 2.0.

 

@Nissim, cool, thanks for the update!