What you need to know
- Foxconn says a custom issue at the Indian border has been resolved.
- Over 150 shipments were held up due to a dispute between India and China.
- It follows clashes at the Himalayan border between the two countries and a series of boycotts.
Apple manufacturing partner Foxconn says that shipments previously stuck at the Indian border have now cleared customs.
Earlier this week it emerged that over 150 Foxconn shipments were stuck in the port of Chennai due to heightened customs checks. The disruption was part of the fallout between India and China, which started as a border dispute in the Himalayas. Widespread anti-Chinese sentiment has led to a series of calls to boycott Chinese products in India, as well as the Indian government banning 59 Chinese-developed apps including TikTok. Both Apple and Google have complied with the order, removing the apps from their respective stores.
According to reports last week, problems with customs clearance had left Foxconn in "a very bad state", and that worked had been staying in their dormitories for two weeks because there was no work to do.
Stephen Warwick has written about Apple for five years at iMore and previously elsewhere. He covers all of iMore's latest breaking news regarding all of Apple's products and services, both hardware and software. Stephen has interviewed industry experts in a range of fields including finance, litigation, security, and more. He also specializes in curating and reviewing audio hardware and has experience beyond journalism in sound engineering, production, and design.
Before becoming a writer Stephen studied Ancient History at University and also worked at Apple for more than two years. Stephen is also a host on the iMore show, a weekly podcast recorded live that discusses the latest in breaking Apple news, as well as featuring fun trivia about all things Apple.
Get the best of iMore in in your inbox, every day!
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.