My Saudi eSIM Had 5G but No Data: The Setup Order That Fixed It

The phone showed 5G. The map showed nothing.

I had just arrived at King Abdulaziz International Airport in Jeddah with my wife, two suitcases and a hotel driver waiting somewhere outside. He had asked us to share our location, but the ride app was blank. The booking confirmation stored in another app would not open either.

Before the flight, I had installed a Saudi travel eSIM and saved its activation details offline. I had also kept my home SIM active so I could receive bank alerts and account-verification texts.

The eSIM found a network almost immediately after landing. Signal bars appeared. I assumed the setup was complete.

It was not.

Messages sat beside a small clock icon. The hotel app kept spinning. When I turned on my regular VPN, it stayed on Connecting.

I blamed the Saudi network and selected another VPN server. Then another.

Five minutes later, I had tried France and Germany, but I still could not load the pickup map.

Signal bars did not mean the eSIM was carrying data

Saudi Arabia received 29. (Com) million inbound tourists in 2025, with religious travel accounting for a large share of those visits. (Datasaudi) Millions of people now arrive carrying digital visas, booking apps, maps, payment tools and family chats that need to work before they leave the terminal.

Saudi authorities and mobile operators have expanded coverage and capacity around airports, major cities and pilgrimage areas. Visitor plans with eSIM support are also widely available for compatible phones. (Gov) (Com)

The infrastructure was not the problem in my hand.

My mistake was treating an installed eSIM as an active data connection.

A dual-SIM phone makes separate choices for calls, text messages and mobile data. One line can remain active for verification texts while the other carries internet traffic. Many travel eSIMs also use partner networks, which means data roaming must be enabled on the travel line.

I had disabled roaming before departure to protect myself from charges on my home SIM. That was sensible. The problem was that I had disabled it for the eSIM too.

I turned off the VPN and opened the cellular settings. My home number was still selected for mobile data. The Saudi eSIM was switched on, but the phone had not assigned it any actual work.

The correction took less than a minute. I selected the travel eSIM as the data line, enabled roaming for that line and left roaming disabled on my home SIM. I also turned off automatic data switching so the phone could not quietly fall back to the expensive home plan. (Apple) (Google)

Then I opened the browser without a VPN.

The airport website loaded immediately.

The eSIM had been installed correctly all along. It simply had not been told to carry data.

That solved the first problem and clarified the next one. The eSIM needed to work before the VPN could protect it.

The eSIM and VPN were solving different problems

At the airport, I had treated the eSIM and VPN as competing ways to get online.

They were actually two layers of the same setup.

The eSIM connected the phone to a mobile network. The VPN protected the traffic moving over that connection. A VPN cannot repair a data line the phone has not selected, and an eSIM does not create a private tunnel by itself.

Public traveller discussions show how easily those roles become confused. People frequently ask whether they should activate the eSIM, join airport Wi-Fi or start the VPN first. (Reddit) The useful answer is an order:

Make ordinary data work first. Connect the VPN second. Open sensitive apps last.

I followed that order and reopened my established VPN.

It connected over the eSIM. The ride app found the terminal, and I sent the driver our location.

For a moment, the problem seemed finished.

Then the phone automatically joined the airport’s free Wi-Fi.

The phone switched networks, and the VPN lost the trip

I had used the airport Wi-Fi on an earlier visit, so the phone remembered it. As we walked toward the pickup area, it abandoned the eSIM and connected to an access point without asking.

The VPN dropped.

The driver’s next message stopped sending, and the location pin froze. I disconnected from Wi-Fi, returned to mobile data and waited for the VPN to reconnect.

Before it finished, the phone found another airport access point and switched again.

The problem was no longer whether the VPN could connect in Saudi Arabia. It had already done that. The problem was whether it could remain useful while the phone moved between the networks travellers actually use.

An airport arrival contains constant handoffs. Terminal Wi-Fi becomes eSIM data near the exit. Mobile data becomes hotel Wi-Fi at check-in. A phone moves between access points at stations, conference venues and crowded pilgrimage sites.

The user sees “the internet.” The VPN sees the path underneath it repeatedly changing.

My established provider had a long public history, broad server coverage and a large support operation. Those strengths were real. But each interruption sent me back to the country map, even though the destination country was not what had changed.

Switching from one server to another could not stop the phone from leaving airport Wi-Fi.

I briefly considered installing a free VPN, but it would have added another login, more server testing and more uncertainty while the driver waited. The problem was already clear enough.

I did not need more locations. I needed a connection that could survive the handoff.

The pickup pin stayed active

I opened OnlydogVPN and selected the travel-oriented situation.

There was no country list to study and no protocol menu to decode. I connected, reopened the ride app and sent the pickup pin again.

The message went through.

As we approached the terminal exit, the airport Wi-Fi weakened and disappeared. The eSIM took over. The map paused briefly, then continued following our position toward the pickup lane.

The tunnel remained active.

The driver replied with the vehicle number. The hotel confirmation opened. I loaded the booking QR code and sent a message to the family group saying that we had arrived.

Those were small actions, but they were the entire reason I had prepared the eSIM before travelling.

Only afterward did I look at why the smaller app handled the transition better. It uses an HTTP/3-based transport that recovers quickly when the phone changes networks, along with additional traffic obfuscation that makes the tunnel less conspicuous on managed or restrictive connections.

The practical effect was simple: moving from airport Wi-Fi to eSIM data did not force the trip to restart.

I could not inspect the airport’s or mobile operator’s internal filtering and traffic-management rules, so I cannot identify every decision made inside those networks. The visible difference was enough. My first VPN needed manual attention after the handoff. The smaller service kept the map, messages and booking flow moving.

The setup I should have completed before landing

Once we were in the car, I realised that buying the eSIM had been the easiest part.

The useful setup depended on four decisions made in the correct order.

First, install the eSIM profile before departure while reliable home internet and the provider’s instructions are still available. The plan may activate immediately or only after reaching a supported network, but downloading the profile early avoids searching for an activation email through airport Wi-Fi.

Second, select the travel eSIM as the phone’s mobile-data line. The home SIM can remain active for incoming texts, but its data roaming should stay disabled unless home-carrier charges are intentional.

Third, enable roaming on the travel eSIM when its provider requires it. Many international eSIMs connect through local partner networks. A blanket “roaming off” setting can disable the plan bought specifically for the trip.

Fourth, confirm that ordinary data works before starting the VPN. Otherwise, an eSIM configuration mistake looks like a VPN failure, and the user wastes time changing servers that were never the cause.

The order is straightforward:

Active eSIM data → VPN connection → travel apps.

Once the first layer worked, the smaller app reduced the remaining setup to one situation-based choice.

That mattered because travel failures rarely happen while someone is calmly comparing specifications. They happen beside a baggage carousel, outside a terminal or at a hotel desk while another person waits for an answer.

The second device did not become another setup problem

At the hotel, I opened a tablet to check the next morning’s route and save offline copies of our booking documents.

Normally, that would have meant finding another VPN password, completing an email verification and checking whether the account allowed another device.

The smaller service let me add the tablet with a verification code instead.

The connection appeared without another conventional login. I opened the route planner, saved the hotel address in Arabic and English, and downloaded the information we would need after leaving Wi-Fi.

This was not the main reason the app had earned a place on the trip. The network handoff had already done that. But family and business travel quickly spreads essential information across phones, tablets and laptops. A passwordless handoff kept the backup device from becoming another account-management task.

The service has fewer server locations, a shorter public history and fewer independent reviews than the established provider I tried first. A traveller who needs a highly specific national endpoint may prefer a larger network.

That was not what I needed in Jeddah.

The major provider gave me more countries to select after every interruption. The smaller app gave the phone a connection that stayed useful while its actual network changed underneath it.

My Saudi eSIM had never needed stronger signal bars. It needed the correct data setting—and a VPN that would not lose the journey when the airport Wi-Fi ended.