nazpaz

I think it's because of information like this from Princess (an email I got today). BTW, I agree that it isn't needed).

Just a quick visual of what I'm getting right before our cruise. Still 6/7 but showing Green.

This Sunday 🙂

I'm sure its dynamic - we cruise on Sunday so we're about as close as you can get! 🙂 Glad to know they are working on it. I'm also 6/7 but if I scroll as described I'm also "Green" to go!

On the new app, just under days to go, there's a "Check-in" tab. If I tap on it, it takes me to the dreaded Shoreside payment method. However, if I don't tap on it but, instead, swipe left, other tabs appear. One of those is "Boarding Pass." It says "proceed to Green Lane." If I tap on that tab, it gives me the check in QR code, and again reports "Green Lane" - as well as other check in information. So, even in the app, if you don't want to provide a Shoreside payment method, you still get assigned to the Green Lane. Anyone want to confirm this on their new app?

Honestly, I originally thought that it was a programming oversight that made it necessary to complete that page to finish everything necessary to order medallions and be in the Green Lane. I still lean that way. However, even though the "glitch" has been reported by many people I've yet to see anything from the company acknowledging that it's unintentional. We cruise this Sunday and I've not filled that page in. However, we had already ordered and received our medallions and show as "Green" on the web and on the old app, so I don't think ours is a proper test. At this point, I'd say that (1) if you don't want to give them that information, and (2) if you have the old app on your device, then (3) go ahead and order your medallions. That way you can avoid the whole question. Otherwise, the company tech people will either fix their "glitch" or, at least the company will clarify their policy as to whether or not the Shoreside payment method is or isn't required.

Your CC will be charged about a month before the cruise. Then, the medallions will be shipped 9-10 days later.

So, if you already have your medallions you are ready for the green lane no matter what the new app says. If you have already booked a cruise you can use the old app or the web page to order medallions no matter what the new app says. If you haven't booked a cruise you can't order a medallion on the old or new app or the web. Is that about right?

I see that the old app now says it will be usable until "early 2024." I think it said February 1 before didn't it?

Happily, the website and the old app agree, so it's 2 votes to 1 that we're Green. 🙂

Sailing next Sunday. My old app has a QR code, and says I'm to proceed to the Green Lane. The new app still wants me to fill in the Shoreside credit card info. I'm sticking with the old app until/unless they fix the new one. Easy enough.

I asked about the Shoreside Payment issue on the Princess "X" page and got a phone call from Princess Customer Service. She wanted to verify for me that I was good to go in the Green line. Also, after having me describe the issue she said that she was reaching out to their Tech team about this issue. She agreed with me that, since we cruise next week, that I needed to keep the old app on my Android phone so I could use it when checking in.

Yep - sorry! I accidentally landed in the wrong thread.

The agent I spoke to today indicated that their tech team was aware of this problem. She agreed with me that keeping the old app that shows us in the Green was a good idea.

I just read that Google Playstore checks for app updates from developers once a day. Apple manages updates. I take it that means Apple can be faster than Google with updates. It will be interesting to see if the Android version updates sometime tomorrow.

It's out of my league but the Android App log-in bug has been fixed - there are multiple reports of it. It was done without requiring an app update. I see that the Apple version information confirms your observation that the Apple app has been updated to 1.0.1. My guess, and that's all it is, is that the Android version could be fixed server side and the Apple version had to be changed client side.

Princess on Facebook and "X" both announced that the login issue was fixed. I can now log in with username and password and not get booted when I go to Check-In on the new app. The app version on Google Play has not updated. It still shows as 1.0.0 I talked to Princess customer service today. The rep was aware of the Shoreside payment method issue. She said she had reached out to their tech support about it. She agreed with me that keeping the old app on my device was a good idea, especially since it shows us in the Green boarding group while the new app doesn't.

Princess Cruises on Facebook says the log out/time out probem has been fixed. I tried it, and so far am staying logged on after signing in with username/password.

You can report this by emailing the app developer at AskOceanMedallion@carnival.com

Me either! At least the old app still says we are green to go.

Have you tried redownloading the old app? While the new one won't show check in complete without the Shore deal, the old one let's you complete check in without it.

I find it under "princess cruises." First thing under the sponsored adds.

What I've found so far: 1. You need to sign in with booking number, etc. if you want to look at Check-in information, otherwise you will be logged out immediately. 2. You can't complete the check-in information unless you add a Shoreside payment method. 3. You can report this by emailing the app developer at AskOceanMedallion@carnival.com 4. If you keep the old app on your device, it can still used and correctly reports check-in status.

I just sent a message to AskOceanMedallion@carnival.com (the app support email address for the new Princess Cruise app). I reported that on the new app Ocean Ready will not complete unless you enter the Shoreside payment method. If others have this issue and report it they might be able to identify this as an issue that needs to be given priority status.

Try logging in with your booking information. That fixed it for me.